You can telnet to the duet and basically do what you want. Before the firmware had variables I made a bunch of. Net apps for various tasks.

@Phaedrux It was a user error. I have two CNC machines. On my old machine I also control the dust extractor. with the M106 command autogenerated from my postprocessor. My new machine has nothing connected so it hits an error, naturally. Still, you pushed me in the the right direction by mentioning other config files, so thanx.

@JuKu In my post I've added so the motors don't idle. At the end of the program I change it back to default.

@gloomyandy

Thanx for all the comment. I'm always amazing how fast things get sorted out when you guys kicks in.

It's generated by Fusion 360 and as it breakt with the gcode spec I just fix it in the post prosessor.

Best regards
Rickard

Hello

When using Fusion 360 and I copy an operation or setup, Fusion adds a (n) to the name of the operation. For example the copy of Contour1 is named Contour1 (2) and so on.

The gcode Fusion generates looks like:

(Contour1 (2))

This results in:

(Contour1 (2))
Error: Bad command: )

And that the line(s) right after are ignored.

I know that I could edit my post prosessor to fix this. But I guess that if this is a parsing issue is should be address in the firmware.

I'm running v3.3 (both firmware and dwc).

Best regards
Rickard

@chrishamm One caveat is that the machine will not pause until the buffer is empty.

@bmeun96 When you telnet to the controllet you get the same functionality as you do with the console in DWC. Connect to the duet with telnet and send some basic gcode to get it up and running. M114 return the current position for example. You have to dive into the wiki.

You can telnet to the duet and basically do what you want. Before the firmware had variables I made a bunch of. Net apps for various tasks.

@phaedrux You can still press a jog button.

This is actually a quite dangerous behaviour. I'm running 2 CNC machines, and on two occasions I've accidentally homed one machine while the other was running. The last time it could have ended quite bad due to the material setup. Now I'm using two different laptops to avoid any incidents. Maybe a checkbox in DWC or a M code to allow or disable manual gcode (or any other source) while the machine is procession a gcode file. With the exception of M112 etc.

@fma said in Using stepper currrent to detect a tool is loaded:

@rzi said in Using stepper currrent to detect a tool is loaded:

@dc42 CNC user here. Is it possible to add. I'm using two free drivers for a motorised vise. Would be super to have a mean of applying same force on each part I'm machining.

You could set the current of the vise motor to set the wanted force (torque). Then, just turn the motor until it stalls (using stallGuard feature, through a homing procedure, for example), and you should get roughly the same force each time.

Ah yes, going to test that. A much more straight forward approach. Thanx

@dc42 CNC user here. Is it possible to add. I'm using two free drivers for a motorised vise. Would be super to have a mean of applying same force on each part I'm machining.