@meeloo

Thank you for the response and sharing your config Im using HY VFD i have a relay board that control the Revers pin and Forward pin basically my setup is out0 for PWM it goes to a PWM -analog converter and out 6 it goes to the relay for forward ,out7 it goes to reverse relay the problem im having that Output 6 and 7 not working they don't send voltage to activate relay I don’t know if its a problem with my 6XD or my pin name incorrect. Thats the issue Im having.

Thank you

@JoergS5 @o_lampe
Thank you greatly for your advice! I have since replaced what I thought was a faulty harmonic gearbox, the backlash in that joint is now greatly reduced. For a university dissertation I had measured the stall torque and repeatability of the harmonic gearboxes, i found stall torque to be around 4.2Nm and precision to be around 0.28 arcmin. A MATLAB simulation model of my parallel SCARA revealed I only needed around 1.1Nm of torque to operate with the speeds and accelerations needed for thin steal.

I am still having some strange behaviours occurring with the machine, circles are still not fully circular, and occasionally joint positions are not achieved in a smooth manner. I am wondering if it's a calibration issue, however I shall now investigate the behaviour of bearings incase they're causing issues. I had previously tried using some sprung lanyards to apply tension on bearings and joints to ensure backlash and engagement is consistent. I will try and post some more pictures of the machines behaviours this evening.

Many thanks!

@Phaedrux will do thank you!

@droftarts said in Cannot run CNC slower than 0.6mm/min:

I'm not sure, either, but the 'maximum time that a move is allowed to take is about 30 minutes" came from @dc42, so probably need his input on that one. I guess segmentation would make it okay?

Correct. Implementing segmentation automatically for long-duration moves is already on my list.

@droftarts Thanks. I'll ask my cousin to check.
In the meantime, he tested the ISO prostprocessor, which seems to work fine.

@lite168418895 you may want to start looking here https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_CNC

@flopes There is the STM B_G431B_ESC board, which works with hardware-encoder for medium power BLDC motors.
It can be flashed with simpleFOC, which allows you to control the motor via step/dir interface by gcode directly or UART messages (for constant speed or torque use cases)

@T3P3Tony I never felt at ease when navigating through various coordinate systems.
Changing a mill bit and setting new z-zero meant pure adrenalin and full concentration for me.
I had to switch through machine/workspace coordinate systems back and forth and without the conditional macros it was all done manually.

Nowadays it's just a matter of writing a bulletproof macro, but I already wrecked my Y-axis because one motor got stuck while the other went on.
IDK if there is a cross check method for stall detection now? (one y-motor stalls and both stop automatically)
When I tried to set it up, I only got popup messages in DWC and had to react accordingly. Fingernail biting time....

@MaxGyver

Thanks for the suggestions i will give them a try, the pitch should be right as i have tested it multiple times over 500mm distances
I will look at the dial indicator

@o_lampe said in on-off control of router using M3 and M5 g-code commands:

@woodcarver I'm wondering if you have to switch the Duet to CNC-mode to allow M3 and M5 commands?

That's correct in firmware 3.4.x and earlier. In firmware 3.5 you should be able to use M3 and M5 in FDM mode too.

@jonas22 does it only vibrate and produce noise, or does it actually move as commanded while it vibrates and produces noise?

@SDJ Yes, it has to run in between 1400 and 2000 RPM which is very slow but for a super short duration (a couple of seconds really) which is not doing much to the spindle, it only has the time to get up to speed.

I currently have a 1.5kW air cooled spindle but I'm in the process of moving to a 2.2kW water cooled one. As I'm going from ER11 to ER20 my current ATC will be for sale as soon as the nice guys at RapidChangeATC send me the ER20 version I just ordered...

(Hehe, yes I have a very inquisitive kid that also doesn't like to follow instructions, he lightly cut the tip of a finger on a sharp router bit right after I told him explicitly, multiple times, not to touch it ;-). Also, he has 3 brothers 😅)

@o_lampe said in Delta mechanism as router:

Maybe I chose the wrong words, but with engraving I meant using a small router and a chisel

No, my misunderstanding. I forget that there is more to engraving than lasers..

And you are right, there is a load of light rotary engraving that could be done.. PCB cutting and drilling springs to mind.

@tierod
hi all, just an update on this script
after changing the if statements to false, with the warning at the end it still gave me the red warning endstops not homed. so i moved it back behind the first if statement and it then gave me the correct blue error message.
it works perfectly this way so unless this is a bad move i’m going to leave it this way.
to reiterate, do NOT have your homing stop on the endstops as it will refuse to move, even 5mm off the endstops and all good.
again, thank you guys for this script!

@o_lampe Hi Lamp - I have been reading lots of stuff and there are oceans to go. Been looking for a clear & simple description on how to connect this to a CNC with servo motors. I'll get there slowly. I think the Duet 3 - 6XD is the starting point...Ta Peter

What are the specs of the motor, and what current are you sending it? Which Duet board?

@WillC1991 Two ideas:

Use M226 in your G-code to pause the file at a given position, then swap the mill, and resume, or Set up different tools in config.g, use a blocking M291 dialog in tpostN.g, and use T0/T1/T2 etc. in your G-code file. See https://docs.duet3d.com/en/User_manual/Tuning/Tool_changing and https://docs.duet3d.com/User_manual/Reference/Gcodes#m291-display-message-and-optionally-wait-for-response

@phoenix There is no infinite rotation in RRF.
But there are workarounds. You can define your spindle as a very long axis. It will take days to reach the end. In a way, this can be considered infinite
Another workaround for G-codes unknown to RRF is to write your own macro.
In your specific case it would be named G76.1
Now you have to postprocess the gcode file you want to run by search&replace G76 with G76.1
When you run the file, RRF will automatically start the macro when the line comes up.
If G76 has some parameters you can postprocess them too, but it gets complicated. Maybe it's easier to write several macros for each thread-pitch you want to cut.

Thank you for the reply- I tried it - Sort Of.

Maybe you can provide some ideas (or the math)..

Bascily I put a 1.3k ohm resistor (dont have 1kohm) between the FAN_Vin and the VAN_pwm(-). I then only connect the pwm signal. No ground to the PWM converter as the Duet and the PWM converter are powered by the same PSU, I suspect the grounds will technically be the same.

Results.. It works - Half way.

My FAN Vin is set to 24v (Input of the duet). And my pwm input is also set to 24v also on the PWM signal. If I measure the DC voltage over the PWM and ground (when at full speed) I get only 14v and not 24. The resulting Voltage after PWM conversion is only 5.5 or something, and not closer to 10.

Does the resistor cause a voltage drop or something? At least I'm starting to get some movement.

@MiguelDK M119 reports the state to the console. If you want to use the state programmatically in meta gcode then the OM keys to look at are:

sensors.endstops[n].triggered