Allows to specify probe block height in cases where it is beneficial to probe non-conductive surface.

Open
#1 · Created  · Last updated

Description

This is similar change as for old Autoleveler. New field to specify probe block height, which is set to zero by default. When computing Z height variables during probing, we subtract value of block height.

Example of generated GCode (probe block height is set at 19.75 mm):

G0 Z25
G1 X9.35 Y9.35 F2000
G31 Z-20 F800
#500=[#2002 - 19.75]
G0 Z25
G1 X16.05 Y9.35 F2000
G31 Z-20 F800
#501=[#2002 - 19.75]
G0 Z25
G1 X16.05 Y16.05 F2000
G31 Z-20 F800
#503=[#2002 - 19.75]
G0 Z25
G1 X9.35 Y16.05 F2000
G31 Z-20 F800
#502=[#2002 - 19.75]
G0 Z25.00000

Considerations:

  • I noticed that you keep certificate signing piece as part of the POM. I would suggest that you have separate toolchain (script) that would take care of signing as it does not pertain to development.

  • I have experienced some odd behavior with arcs in gcode on my controller with generated autoleveled code(USB controller). I’m still figuring what is wrong, though I did run smaller example of code (cutting half inch hole) without problem. Nevertheless the problem appears to be yet identified.

  • Not a fan of JavaFX. Five times amount of work for the same interface as QT library. Literally spent 50% of time for this code change battling JavaFX Scene Builder to get some decent behavior.

  • Java 10 SDK does not work with your code due to dependencies not fully supporting it.

  • There appears to be freezing on main thread for ‘Mesh Settings’ dialog. Didn’t investigate, but only appears with standalone executable and jar (not through running code directly from IDE).

0 attachments

0 comments

Loading commits...