Here's the updated connection diagram:

Screenshot 2022-12-02 at 18.30.44.png

...and this is the code from the config.g file:

; Milling motor and relay configuration M950 R0 C"vfd+out7" L4000:25000 Q1000 ; enable router relay on out7 M563 P0 S"St George" R0 ; assign spindle 0 to tool 0 and name it St George T0 ; select tool 0 M5 ; ensure motor is turned off

Note: I have used this relay to provide mains power to the milling motor, which is activated from Out7 in this case. I guess any Out could be used, but the code would need to be changed accordingly.

Many thanks to @dc42 and @jay_s_uk for helping me resolve this, and I hope this diagram will be of use to others.

Sorted it and dancing around the workshop .
Looked at all the frequency settings on VFD and noticed that PD011 was set to 200.00. Set it to factory 0 and it all works.
Thanks so much for all your help. This forum is invaluable.

@peteupshall also read https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_CNC#connecting-a-spindle.

@peteupshall I do XYZ probing on my milling machine.

A - I have a physical endstop for each axis (XYZ) that lets me set a physical origin. These, with config.g settings, are used to set up the physical bounds for the machine.

B - when milling I use the XYZ probing to set the stock origin.

I've considered using XYZ probing to set the physical origin and boundaries but really there's no easy way to do that initial probe automatically without endstops so never bothered setting it up.

There's a writeup in my personal wiki (with script for the probe and results of physical tests) here: http://eadia.com/pmwiki.php?n=Taig.Probing

Mark

My Globals settings for the probe->

; global <new-variable-name> = <expression> ; touchpad center and height global TouchX = 15 global TouchY = 84 global TouchZ = 13.125 ; the touchpad Z offset from ground ; speeds for probing global ProbeFastZ = 400 global ProbeFastXY = 300 global ProbeSlowZ = 200 global ProbeSlowXY = 50

Here's my Z probe code (I use the bed location usually, so) ->

G53 G0 X{global.TouchX} Y{global.TouchY} G30 S-1 ; lower z until the metal probe is hit G10 L20 P2 Z{global.TouchZ} ; Z = 0 + puck height in second coord system G1 Z38 F600 ; raise z one inch

Here's my X probe current code (with a 1/4" bit)

; probe with 1/4" bit m98 P"0:/macros/Finders/FindXPlus.g" d0.25

And the submacro:

var dir = 0 var movs = -2 var multip = -12.7 if {exists(param.S)} set var.dir = param.S if { var.dir == 1 } set var.movs = 2 set var.multip = 12.7 if {exists(param.D)} G91 ; relative moves m585 S{var.dir} X-50 F{global.ProbeFastXY} P0 ; probe until contact X G10 L1 X0 Y0 ; reset the tool offset created by m585 G1 X{var.movs} F{global.ProbeFastXY} ; back off m585 S{var.dir} X-50 F{global.ProbeSlowXY} P0 ; probe until contact X G10 L1 X0 Y0 ; reset the tool offset created by m585 G10 L20 P2 X{param.D * var.multip} ; subtract half the bit diameter G1 X{var.movs} F{global.ProbeFastXY} ; back off G90 ; absolute moves ;G1 X-12 F600 ; back off else M117 FindXGen requires a D(iameter) parameter

@JoergS5 said in Unable to control Spindle with Duet 2 WiFi:

https://www.cnczone.com/forums/spindles-vfd/426990-cnc-forum.html

Thanks, yes the 48v power supply I am using is earthed and I am using a dc spindle.

I've done a little drawing, so perhaps this will be of use to someone in the future...

1670005889542-screenshot-2022-12-02-at-18.30.44.png

Enjoy!

Edit: Changed image to the real one!

@fishgrog Our software stack is fully open-source so you can already modify DWC as you like (see here provided you can get into Vue 2).

HTTP calls in standalone and SBC are documented as well, see here for standalone and here for SBC mode. DSF v3.5 will support compatibility for standalone HTTP calls, too.

@dc42 Thank you

@Nightowl said in Big ask... Z probing:

G1 Z{max(move.axes[2].userPosition+5,move.axes[2].max-5)} F2400 ; move the Z axis to 5mm below Zmax

I think that first max should be a min, in case Z axis is already at max.

You will also need to use G31 to set the trigger height of the Z probe, normally in config.g after the M558 command.

You can use G60 to save the position before probing, and G0 with the R parameter to go back to that position or a related position.

See M290 in the gcode reference

@ecncshop said in 5-axis CNC/FDM: Tool vs Machine Coordinates (Inverse Kinematics):

Does that mean fusion 360 does not have this option to calculate the RTCP and output gcode

I didn't know that there is a "machine extension" in Fusion and that you're using it. Maybe it can support RTCP mode, it looks like a powerful extension.

@chimaeragh I want to make a macro that interrupts the work in progress (doesn't have to be able to continue) and moves the blade to these coordinates. How ???

@Sindarius @chrishamm Thank you for the feedback on this!

@MaxGyver I'm not a lathe user so I looked up constant surface speed online. I see what this does - the spindle RPM depends on the distance of the cutter from the center such that the surface speed stays constant at each distance.

You're right that Duet3d RRF does not support that. It wouldn't be that tough to implement but I'd bet it's not on their current plan since it's very lathe aware.

@chrishamm said in M911 on a CNC machine:

@Nightowl Are you running your Duet in SBC mode? If yes, you may need to attach a really beefy 5V power supply to maintain power for both boards long enough so that the resurrect file can be safely written. Also note that calling macros from M911 is not really a good idea unless you have a decent separate 5V supply because that will introduce more IOPS which in turn slows down the whole saving process.

No Chris, it's connected to a Surface Pro, which is powered independently and has an internal battery, so would keep working in the event of a power failure.

What might be relevant is that the laptop and controller are connected via a powerline adapter, so if the power fails the connection would be lost (the laptop doesn't have a network connector, so I have to use a dock). Maybe I should think about connecting via USB... 🤔

@chrishamm said in M911 on a CNC machine:

@dc42 It looks like workplace coordinates are written to resume.g but not spindle speeds. Should that be added in v3.5?

I seem to recall @dc42 mentioned this when I first asked the question "back in the day", when he said this would be incorporated into v3.5, so I'm keeping my fingers crossed...
(https://forum.duet3d.com/topic/28647/power-failure-and-resurrection-on-a-cnc-machine/102)

@alankilian

I followed your suggestion and a lookup table to pick the initial potentiometer position and then fine tune the spindle RPM with a loop.
This worked well enough for some initial tests. But for me, it was no satisfying permanent solution.

After taking some voltage measurements, I figured that the motor controller simply needs a 0-5V Control Signal. 🤦

So I used a PWM to analog converter to provide the control signal and to galvanically separate the inverter from the Duet Board.

I am using a multifix toolpost to quickly change between tools. In order to avoid manually calibrating a new tool, I wrote a macro that can automatically set the offsets for a given tool using a touch probe. Since the multifix toolpost is very repeatable, the offsets do not need to be recalibrated after a toolchange.

IMG_20220809_180950.jpg

I am very happy how this project turned out. The Duet3HC is a formidable controller for small CNC-Maschines. 😀 👍

Video: Paulimot CNC-converion test.mp4

IMG_20220919_204618.jpg

IMG_20220921_202237.jpg

Cheers
Max

That's great information, thank you @markz

I would comment out the last two lines and then add a line to run the end.g macro, to send the spindle to its safe position, then.

I imagine this should work:

+--------------------------------------------------- + Commands output at the end of the file +--------------------------------------------------- begin FOOTER "M5" +-- "G0[ZH]" +-- "G0[XH][YH]" "M98 P"end.g""

With the end.g macro looking something like this:

; end.g G1 Z{max(move.axes[2].userPosition+5,move.axes[2].max-5)} F2400 ; move the Z axis to a safe height G0 X273.5 Y560 ; move XY to a safe place

I'm still working on the probe macro...

@Sejl you don’t need a special post processor, just use a fanuc one and remove the canned cycles. All the Gs and Ms in every line are no longer needed, it behaves as a normal industrial Cnc, once a command is sent, all the lines following are under that command, unless you change it again.

@ian-0 Hi, I don't think it's skipping steps. That would produce some of the desired path.

I'm not entirely clear on what it's actually doing. Are you saying that it cuts the two grooves we see then comes back and cuts them again and again and then it stops? That would be bizarre. It could be that it's deciding the cnc hasn't parsed those two chunks and it sends them repeatedly until it gives up I suppose.

I'd also vote for seeing your config.g file for RRF.

One simple test you could do is manually move the CNC head - following along the G-code roughing file - just send each line individually in the console, except the Z offset, (without the N prefix) and see how the head moves.

mark