nunorvoliveira / snapmaker-2.0 Goto Github PK

Is your feature request related to a problem? Please describe.
It's annoying and time consuming to measure tool lengths manually with the calibration card. I'm looking for a neat way to measure tool length and calibrate them easily.

Describe the solution you'd like
My idea is to use something like this: https://www.sorotec.de/shop/Werkzeuglaengensensor-Sorotec-8mm.html and connect it with a LED. Once the Z is lowered to the point you need, the switch closes and the LED lights up. Using the knowledge we have of the tool length sensor, it might be possible to add a manual NC command to Fusion to offset the Z by this value. So for example, I'm setting my origin to:
X:150
Y:30
Z:68
Manual NC Action "Z_AXIS_OFFSET -8" is being added and converts it to:
X:150
Y:30
Z:60

This could be extended for a toolchange. If my first operation is an adaptive clean with a tool that has a 50mm length, I'm calibrating the Z with "Z_AXIS_OFFSET -8". Then I'm changing over to a tool with 40mm length and I would add "Z_AXIS_OFFSET -18".

Hi, wondering if the post-processor always sends to work origin?

I sometimes set my work origin to be under the part (makes setting the z-origin pretty easy). This may be a horrible practice, but wondering if I should avoid doing that if I'm using this post-processor.

Is your feature request related to a problem? Please describe.
I noticed that the .cnc files given by Fusion 360 using the Post Process there are a few things missing that are in the .cnc file provided by the Luban Software when it creates a .cnc file.

While it is not necessarily a problem it does open up an opportunity for the Fusion 360 Post Process to get closer to being similar to how the makers of Snapmaker have designed G-code files for their CNC machine. This is particularly helpful when still using the Luban software to preview G-code. Also using the software to send it to the Machine.

Describe the solution you'd like
The solutions would be to take the exported .cnc files provided by Luban Software and working the format it into the Fusion 360 Post Process. Luban provides a set of "header" comments (example below), could this data be worked into the Fusion 360 Post Process? For example what Luban calls "Work Speed" Fusion 360 calls "Cutting Feedrate".

;Header Start
;header_type: cnc
;tool_head: standardCNCToolheadForSM2
;machine: A350
;renderMethod: line
;file_total_lines: 751
;estimated_time(s): 403.288
;is_rotate: false
;diameter: 35
;max_x(mm): 147.32999999999998
;max_y(mm): 73.634
;max_z(mm): 80
;max_b(mm): 0
;min_x(mm): 9.920000000000002
;min_y(mm): 9.864
;min_b(mm): 0
;min_z(mm): -2
;work_speed(mm/minute): 300
;jog_speed(mm/minute): 1500
;power(%): 0
;work_size_x: 320
;work_size_y: 350
;origin: bottom-left
;thumbnail: data:image/png;base64,iVBORw0KGgoA...
;Header End

Describe the bug
The command ACTION_PAUSE_RAISE_Z raises Z to 9999 ->

// Raises Z axix to Z9999
                writeBlock(gMotionModal.format(1), zOutput.format(9999), feedOutput.format(200));

Could we reduce this to the max Z height that Snapmaker is capable of? Luban would benefit from it, as this currently breaks the preview and the time calculation on the machine itself.

In addition, could we increase the speed before the Z raise? I think at the moment it uses the last feedrate set.

However, thank you very much for sharing this! This already helped me alot!

I'm wondering what, if anything needs to be done to support the new CNC module that Snapmaker has released for 2.0. I'm assuming at this point all that needs to be done is adjust the spindle speeds?

If not, would be happy to contribute! but wanted to check in ahead of receiving my new module.