New version of G29 probing

[toddwagner]

Firstly, I'm sorry if this is in the wrong category, wasn't sure if I should put this in general or firmware wish list.

I have been thinking lately about the G29 probing radius on my delta. When I am printing a 200mm by 10mm rectangle, it seems wasteful to use a 100mm radius probing circle at 10mm probe point spacing if the only area of the bed that I will print on is that 200x10 rectangle. If only there was a way that I can set a probe field that only covered the area I am printing on. I would then be able to decrease the spacing between probe points and get more probing per square cm on my part than if I use a circle of 100mm radius.

Is it feasible to make an option in the g29 command that would evaluate and probe the area only covered by the first layer? Or maybe even more parameters in the command itself that we can enter to constrain the probe area and better suit the shape of the object we are printing?

Thanks,
Todd

[dc42]

What would be better is if the slicer could generate a comment giving the maximum and minimum X and Y positions.

I am considering having simulation mode write a comment to the end of the GCode file to give the calculated print time. It would be possible to have it write a min/max coordinate comment at the same time.

[wilriker]

@dc42 said in New version of G29 probing:

I am considering having simulation mode write a comment to the end of the GCode file to give the calculated print time.

Sorry for abusing this topic, but I would love to see the above! Currently this information is lost - or at least I have not yet found it after DWC was reloaded and thereby lost console history.

[Phaedrux]

@dc42 That would be great. I've gotten both Cura and Slic3r PE to give pretty accurate time estimates now to within a few minutes of the simulated time, but there is no way to view those time estimates later on. Does the DWC store any meta data for the g-code files or is it only what it can pull from the G-code file itself?

[dc42]

DWC only displays info that RRF finds from the GCode file.

[Danal]

@phaedrux said in New version of G29 probing:

@dc42 That would be great. I've gotten both Cura and Slic3r PE to give pretty accurate time estimates now to within a few minutes of the simulated time, but there is no way to view those time estimates later on. Does the DWC store any meta data for the g-code files or is it only what it can pull from the G-code file itself?

Opening few lines of a Cura G-Code file:

;FLAVOR:RepRap
;TIME:38846
;Filament used: 43.3466m
;Layer height: 0.2
;Generated with Cura_SteamEngine 3.2.1

Time appears to be in seconds.

[dc42]

Added to the work list.