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

jml

@dc42 Instead of manually creating a dummy .csv height map in excel. I thought when you said "You'll need to generate a dummy height map file" I thought that meant manually create it in Excel or TextEdit. But maybe I mis-assumed!

dc42

If you create a tiny height map, then outside the bounds of that height map it will extrapolate, which is likely to give poor results.

jml

@dc42 can you clarify whether I should make the height map manually in excel, or if I should make it using M557?

Phaedrux

@jml I think either way you do it, don't make it very small.

jml

Ok I wasn't sure if one way was the wrong way.

jml

Well I'm not sure if M557 X0:200 Y0:200 S1 will actually create the height map with zeros everywhere, or if there is an extra step after that to populate it with zeros.

Phaedrux

I think you would have to either run an actual g29 to get it to output a height map you could edit or you'd have to just create your own height map from scratch.

jml

This post is deleted!

jml

Just playing with baby stepping, I have made a short g-code file to move back and forth slowly in the x dimensions (80mm back and forth).

I see that if a G4 command is 5 lines away from the current move, then the baby steps will not execute until after the G4 command has passed.

Normally they will execute after the current move (or "after 500ms is passed, whichever is greater").

I also see that the z axis doesn't just move up right away ... it spreads out the height adjustment across the next move.

This is all without the height map file, so now I will test with the heightmap file (if I can create it successfully. Can someone post their heightmap.csv file so I can base mine off that?

Phaedrux

@jml 0_1536647204948_heightmap.csv.txt

M557 X10:280 Y35:270 S15

jml

Adding the heightmap.csv file into the /sys folder didn't change anything - probably I made the file incorrectly or config is wrong.

In config.g I put this near the beginning of the file:
M557 X-100:300 Y-100:300 S1
G29 S1 ; load heightmap.csv

And then in heightmap.csv, I have what I think is correct based off what I see others do online. But it didn't seem to change the behavior at all - I'm still not able to babystep the height during long moves.

Phaedrux

I'm not sure about using negative values in M557 unless you intend it for areas off the bed? Do you have negative values for your axis minima?

jml

@phaedrux No negative values, but I assumed the map could extend beyond the actual print bed boundaries.

I'll change it to M557 X0:200 Y0:200 S1
But then in the csv file, should xnum and ynum be 200, or should it be 201? xspacing and yspacing should be 1, and xmin/ymin and xmax/ymax should be 0 and 200 respectively, right?

Phaedrux

For it to work it also has to have a grid spacing that generates only as many probe points as it can handle. I think the limit is around ~~4000~~ 441? So spacing of 1mm is probably way too low. Try 20 or 30mm.

fcwilt

The docs on M557:

https://duet3d.dozuki.com/Wiki/Gcode#Section_M557_Set_Z_probe_point_or_define_probing_grid

For Duet WiFi/Ethernet it lists the max points as 441.

Frederick

Phaedrux

@fcwilt Thanks. I knew there was a 4 in there.

fcwilt

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

@fcwilt Thanks. I knew there was a 4 in there.

Hey what's a few thousand one way or another among friends.

Frederick

jml

So I finally made the csv file correctly (I think), with 21x21 zeros, and in config.g I set it and load it:
M557 X0:100 Y0:100 S5
G29 S1 ; load heightmap.csv

But, as soon as I home either X or Y, the printer freezes.

If I comment out G29 S1 in config.g, and restart, everything is back to normal. And then if I send G29 S1, then G29 S2 (to load heightmap, then forget it), everything is still fine. But if I I do G29 S1, then home X, then do G29 S2, the printer is still frozen - no commands or buttons (from DWC at least) seem to work other than the Emergency Stop button.

Phaedrux

@jml it would seem that your heightmap.csv is malformed in some way.

jml

@phaedrux 0_1536706534660_heatmapXLS.xls

normally the file is a CSV with the name heightmap.csv , but its xls so that it can upload here.

Thats weird that when uploaded, it called it heatmapxls.xls. Anyway, is there something terribly wrong with my heightmap.csv file?