Preview version of CNC optimized DWC.

cjm

@sindarius That sounds a neat and simple solution!

chimaeragh

@sindarius Thanks for the quick update. Will be testing in the morning

Sindarius

@chimaeragh No problem, I don't want anyone breaking bits on my watch Blown up a couple carbide bits in my day!

paulg4h

@sindarius said in Preview version of CNC optimized DWC.:

@paulg4h let me take a look but I imagine that should not be a problem.

Many thanks again!

With the latest Version 3.3.0-CNC07 the Temperature and Flow are now shown in DWC!

chimaeragh

@sindarius Tested today and everything works great . Thanks a lot

I had to modify my workzero.g file, I found my Z axis moving up and crashing whenever I used to Go to Zero.
The offending line was

G1 H1 Z1500 F2400

before the X and Y axis movement.

I replaced that line with

M98 Phomez.g

and it's working OK now.

Sindarius

@chimaeragh I need to double check but you may want to try G0 H4 when you go to move to the top of the z axis. Worth a shot at the very least.

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

chimaeragh

@sindarius I have tried that, but I seem to lose my current Z zero position so I've commented it out and gone back to calling homez.g which works fine

chimaeragh

@Sindarius I have just noticed that tool position coordinates do not update in real time, but only after starting a new segment of gcode. Is this intentional or a bug?

Sindarius

@chimaeragh The position is how it is reported through the object model. What I normally see is tool position updates when the move starts and machine position updates after a move has completed. It's not a DWC-CNC specific behavior.

chimaeragh

@sindarius OK. I think it worked differently on RRF2. Curious why it was changed but it's not too much of a problem.
Jogging updates in real time though

Phaedrux

@chimaeragh I'm not sure it was any different in RRF2 though.

In RRF 3.3 you could try decreasing the segment size to make for smaller move lengths. That might let it update more frequently, but I'm not certain. See M669 S and T

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_Parameters_for_Cartesian_CoreXY_CoreXZ_CoreXYU_CoreXYUV_MarkForged_kinematics_RRF_2_03_and_later_only

Sindarius

@chimaeragh

G91
G1 H3 Z90 F500
G90
G1 X0 Y0 F6000
G1 Z0

I set this up on my test CNC machine and it worked fine for a go to zero macro. you can set the Z value greater than you z travel and it should stop when the limit is hit.

chimaeragh

@sindarius Thanks

chimaeragh

@Sindarius @dc42 @raymondstone Has anybody been able to get power loss resume working with the latest release? Maybe a macro if not implemented in the UI itself? I'm able to run some very long jobs and I'm very nervous as utility power supply is not quite stable at the moment.

chimaeragh

@chimaeragh Found it. Simply sending M916 via console was the solution. Thanks everyone. Should always search the wiki before asking dumb questions

bitminter

@sindarius any updates on the probe integration? That would be very helpful to say the least thanks again for all your hard work!

chimaeragh

@bitminter There's a probe plugin available now here...

CNC Probe Plugin

bitminter

@chimaeragh that is AWESOME!! Trying it out now! Thanks again!

Shanian79

1 year with the Duet3 running the CNC. undefined

JoergS5

This post is deleted!