@dc42
Does the firmware or the board have lower limits that do not allow stepper motors to be handled slowly?

@mae18 If you bought the rotary axis from Workbee, they should be able to help you with the wiring and configuration. Otherwise, we're going to need quite a lot of info:

Duet hardware and firmware version - send M115 in the console and post response The config.g from the Duet A picture of the Duet, so we can see if you have a spare stepper driver (you should do)

Post code as text, preferably using the code tags in your reply (the </> symbol in the text styles panel above where you write your post) to make the code more readable, rather than posting screenshots of code. For example:

This is a code block

You can always edit your reply to get it looking right. This will help people help you!

Ian

@mattyd to set X0 Y0 to set the bottom left and positive movement to be correct you should do the following:

Set the motor directions using the M569 commands in config.g (or in your case, probably in config-drives.g) so that positive X is to the right and positive Y is away from you. Change the M574 commands to set the endstops to low-end (e.g. X1) instead of high end (e.g. X2). Change your homing files to move in the negative direction instead of the positive direction.

See https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_cartesian. I am assuming that your machine is Cartesian, not CoreXY.

@jay_s_uk said in Correct way to setup dust extractor:

@TQKez-0 M7 isn't supported by RRF, but you can add support for it yourself.
just create a file called M7.g and put it in sys, with whatever you want to happen as its contents.
Then, when M7 is called, the contents of that file will be processed.

Oh thats great!

@bruce This is much better than other Fusion PP's I've experimented with, but I have the same problem as I do with all the the Fusion post processors in that it tries to do the first move into position without lifting the spindle.

Once it gets to the first ramp down position, it moves the spindle up first before plunging, but it's already too late as it's crashed into the stock on the move and snapped the end mill.

Not so hard to fix manually by inserting the appropriate move command just before the first G0, but its easy to forget.

Is there a setting I'm missing that would make raise the spindle first (ideally to Z Max, and ideally also after a tool change) by first moving the spindle up and out of the way of the stock and clamps.

Thanks.

@gloomyandy @dc42 thank you for your posts. im now in the clear. please mark solved.

Please mark solved,

@Aquilux A simple thanks but no thanks will suffice.

I'm necroing this because while it's an edge case it's still a problem.

There's a bug report on git hub that was closed because no one replied in time and it says to open an issue in the forum if it's still a problem, but I'd rather keep a discussion going rather than clutter things with new issues on the same topic. Needless to say generally having a move command not respect what type of move you're commanding and moving unexpectedly is a problem, moreso in the CNC world than the printer one, and my post on the bug details exactly how this has impacted me (my own experience is quite similar to @Max3D 's but I was lucky enough to notice why sooner). I would request that we get some attention to this soonish.

@DigitalElf I suggest you check what stepper motor current is being set. If it's more than 2000mA then you should consider using a fan to cool the Duet - see https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#cooling. Otherwise I can't think of any reason not to move the Duet if you take the usual precautions, e.g. use thick enough wires for the current they carry, and for those wires that go between static and moving parts restrain the cable at both ends to avoid it being flexed at the connectors.

@maletecsci i think it may be enough to set up the same driver as E and U, so something like
M584 X0 Y1 Z2 E3 U3 P3 with the U axis settings matching the E settings in the rest of the driver settings
That will hide the U axis by default.
Then in your homing file at the beginning, set M584 P4. That will unhide the U axis, allowing you to home it using G1 H1 Ux etc.
Then just rehide the U axis at the end M584 P3

@Mastermark said in Trigger Macros using Arduino + Buttons:

@deckingman Sorry i forgot to mention i have the Duet 2 Ethernet

In that case, you'll likely be limited to using spare end stops. If that's the case, then IIRC there are 5 available on the board of which you might be using a couple, but I think there are another 5 on the expansion connector.

@sonderzug unfortunately no license on https://github.com/sb-ocr/diy-spacemouse so no usage rights for nobody.

@HebigT Which Duet 3 are you using?

I had a Google around, but there's really very little info on this spindle as far as I can see. The best info seems to be in the snapmaker forums, ie https://forum.snapmaker.com/search?q=cnc %23snapmaker-20
I found this thread where someone had take the module apart, and has some information: https://forum.snapmaker.com/t/cnc-spindle-not-running/24696
Someone replied:

The FG pin is the frequency generator internal to the motor that tells the machine how fast the spindle is actually going and is irrelevant to what you need.

So the FG pin is the tacho, but you'll need to put an oscilloscope on it to check the voltage and signal, I would guess, once you get the spindle turning. If it's within specs, you could set up a dummy fan and connect this to a the dummy fan's tacho input. While the Duet can accept a tacho input, it would need to conform to the Intel PC fan specification, which expects 2 Pulses Per Revolution (PPR) from the tacho, and the RPM reading calculated assumes that.

The PWM pin should set the spindle speed. The thread above talks a lot about 5V and 3.3V traces on the board; try 3.3V PWM, then 5V if it doesn't work. Try using the Laser/Servo/VFD pin, which provides a 5V PWM signal. All other PWM signals switch on the ground side, so you need a circuit to pull them up to whatever voltage you need to drive the PWM signal. Also try different PWM frequencies (Q parameter in M950).

Again, you'll have to play around with the Direction pin. I guess it's either high or low. So leaving it disconnected should get it spinning one way. Applying a voltage would, I imagine, make it spin the other way. Though it's also possible it is an enable pin, so needs a voltage to work.

For testing, you could set up a PWM pin to drive the motor only. Use M950 to create an output (use the Laser/Servo/VFD pin) and control it with M42. See https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_servos#connecting-dc-motors

For actual configuration, see M950 and M453. There's also this page: https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_CNC

Ian

@o_lampe said in tangential knife support? Newbie questions:

@droftarts said in tangential knife support? Newbie questions:

The oscillation motor appears to need a voltage signal (it may work with PWM, but may need a PWM to voltage converter) to control the speed

It probably isn't a motor but a simple solenoid/linear actuator? That would work with PWM when driven directly by Duet (heater port)

//edit I should've checked the product page. Why do they use a heavy stepper for such a simple task?

not a clue! though I think on their main desktop cncs they use two motors for each axis.

@danny_swbc What firmware version are you using? Send M115 and post the response. Your config.g calls another file, customconfig.g. Is there anything in that? Please also post your resurrect-prologue.g and latest resurrect.g files.

Have you read through the advice in the wiki page here? https://docs.duet3d.com/en/User_manual/Tuning/Resume

From the above wiki page, to use the resurrect.g file, you send M916:

After the power is restored, you can use command M916 to resume the print from where it stopped. This command runs file sys/resurrect.g which calls sys/resurrect-prologue.g at an appropriate point to home the printer

If you pause during a job, does it create a new resurrect.g file (it should)? Delete any resurrect.g file then test by turning off power during a job, does it create a resurrect.g? If you're connected via DWC, it should show whether a resurrect.g is saved.

The resurrect.g should save all the workplace coordinates in it. While I don't use workplace coordinates in my test setup, I've just tested the functionality, and it is working in the current firmware. This is the resurrect.g that was created:

; File "0:/gcodes/x_carriage_IAN.gcode" resume print after print paused at 2023-06-26 12:48 G21 M140 P0 S60.0 G92 X16.119 Y7.463 Z3.600 G60 S1 G10 P0 S195 R200 T0 P0 M98 P"resurrect-prologue.g" M116 M290 X0.000 Y0.000 Z0.000 R0 T-1 P0 T0 P6 ; Workplace coordinates G10 L2 P1 X0.00 Y0.00 Z0.00 G10 L2 P2 X0.00 Y0.00 Z0.00 G10 L2 P3 X0.00 Y0.00 Z0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 G10 L2 P9 X0.00 Y0.00 Z0.00 G54 M106 S1.00 M106 P0 S1.00 M116 G92 E0.00000 M83 M486 S-1 G17 M23 "0:/gcodes/x_carriage_IAN.gcode" M26 S706324 G0 F6000 Z5.600 G0 F6000 X16.119 Y7.463 G0 F6000 Z3.600 G1 F1800.0 P0 G21 M24

This is the console output in DWC from turning off the power in the middle of a job:

26/06/2023, 12:48:20 M0 Printing paused at X16.1 Y7.5 Z3.6 Cancelled printing file 0:/gcodes/x_carriage_IAN.gcode, print time was 0h 2m 26/06/2023, 12:48:18 M25 Resume state saved 26/06/2023, 12:45:19 M916 File 0:/gcodes/x_carriage_IAN.gcode selected for printing 26/06/2023, 12:43:30 Connection established 26/06/2023, 12:43:16 Connection interrupted, attempting to reconnect... HTTP request timed out 26/06/2023, 12:43:07 Resume state saved Print auto-paused due to low voltage

getting really frustrating now especially with a few power cuts each month that invariably happen when work is on the machine

To be honest, if it's happening that frequently, I think complaining to your electricity supplier and/or a robust power backup solution would be better options.

Ian

@xavierb

I removed the M501 at the end of my config and deleted my config override. I'm a bit sketched out that this might have some unforeseen consequence, but this will have to due for the moment