@dc42 thank you for your reply G80 is cancel canned driling cycle so without g81,2,or 3. there is nothing to cancel. g80 is just cancel there are no parameters or switches in iso gcode.

please give the option to use either wear or diameter comp, with diameter comp usually all your lead-ins require a linear move equal to or greater than of the radius of the tool this is a pain in a small hole but there are people out there that love it. i prefer wear comp less can go wrong .000 wont crash your part like in diameter mode.

feed hold would probably get me to swap my linux cnc setup on my router to robot arm and use my duet 2 on router.

Thanks 🙂

@dc42 Glad we caught it before the stable release, thanks man! Excellent work as always 🙂

@t3p3tony said in disallow non-travel moves while spindle is off?:

so this would need to be configurable on a tool by tool basis (which tool change macros could do).
The feed stop trigger would come from a tacho or similar on the spindle or from a spindle off gcode being sent (or both)?

That sounds reasonable. Possible have a dedicated global flag/variable that permits or blocks G1 moves without spindle rotation?
Or, add a "tool type" variable for each tool, that can be used for multiple flag bits.

The feed stop at spindle stop could be triggered by M5 or any manual spindle stop control.

Any fault signal from the drive should cause a complete program stop.

Another normal interlock is that feed hold is asserted (or the M Code complete is not set to allow the NC to continue) during an M3/M4, until the spindle has reached its set speed; either by monitoring a drive signal such as "at speed" or "not ramping" , or just a time delay to allow the speed to settle.

That is sometimes also done on an M5, typically for safety at a program end, so everything has stopped before the CNC acknowledges end of program and the operator can intervene.

@gabit Thanks, now it works!

Yess!! Adding that code to the config.g indeed did the trick! It works like a charm now!!

Thank you Raffers and Dhusolo for the suggestion!

Yes i tryed it , the speeds are even, same problem . Now i will try with slow instantaneous speed changes - around 100 to see if there is any change.
I am not sure about kinematics, i rely on only the CAM software, should i change any kinematics setting on duet ?
This is the configuration of machine:

IMG-6139 - Copy.jpg

@chimaeragh

It's just my opinion, but if it's a safety-critical thing, an Estop button should kill all AC power to the equipment it's intended to stop.

Software-controlled Estops should really be labeled "stop-suggestion" button.

@dc42 7C34FC9E-1A9D-48E9-A3A1-AE4046775563.jpeg 401B3BEA-00FF-4E48-BB3A-B4832FA7AE6C.jpeg E47382F1-E0DA-49B3-983E-A65DCAE58FB7.jpeg

@dc42 Yes now I've got the data down to a reasonable size I can parse and select what I want.

Thanks again.

@siam thank you so much. I never saw that chooser.

My guess is that option was set to something not in the list (due to 3.3/cnc install) so Dashboard Mode just looked like a radio container name - it had nothing in the list showing. Once I selected Default (or FFF or CNC) it then showed the contents.

@dc42 Thanks, that’s easy enough to work around for now. Been thinking about putting the message in the file that calls G28 anyway.

Yes, the DWC doesn’t handle lower case letters.

SBC mode doesn’t work at all last I checked.

M208 had some weird behaviour. I’ll bump that thread.

@dc42 IT is great news , Would it work with duet 2

@thomas-weiss said in M915 not triggering under any circumstances:

Alright. I just did some testing. Setting M569 to V20-V50 makes it trigger stalls, but the motors seem to be incredibly weak and loud even at 2200 mA current. They are basically just stalling themselves in an aircut without doing any actual milling.

I'm not really surprised. When the driver run in stealthChop mode, it switches to voltage-controlled mode, so that the current is reduced and the motors are quieter. The ability of the motor to respond to large increases in load is compromised. For example, when 3D printing if the nozzle hits a blob or overhang, missed steps are more likely if the driver is operating in steathChop mode.

In a milling machine the difference in load between homing (when the tuning cycle is done) and milling is much greater than the load change in a 3D printer. So I am not surprised that stealthChop mode doesn't work well for milling.

Additionally, stall detection doesn't work well at low motor speeds, because the back emf due to rotation isn't high enough to distinguish reliably from the other voltage drops in the motor.

Drivers that do stall detection in spreadCycle mode (such as the TMC2660 on the Duet 2, or the TMC5160 on Duet 3 MB6HC) may be more suitable for stall detection in a milling machine; however the low motor speed might still make it unreliable.

Alright, some results. This works:

output.print(((float) distance)/100); output.write('\n');

It was just the \n that was missing. I like this solution since it's very easy to read and modify the scale factor. And by using float you can have none-10 factors if you want. It does add about 1400 bytes to the program size, but that still only brings it up to 29% of total so it doesn't really matter.

Not sure though how many decimals are actually printed, since I don't have access to a ttl level serial monitor. I read something about two decimals being default in Arduino. For CNC use it is entirely possible some users would want 3 decimals.

About the machine lag, I did some more testing. if I change just one of the axis to use g0 while the other axis uses g1 I can't provoke it to start lagging. Which doesn't make sense, if I jog an axis that uses the g1 command it should still behave the same. Maybe it's just so sporadic that I can't figure it out, sometimes I can't make it lag and sometimes it's barely usable. Are G0 and G1 moves planned differently in any way? Maybe this theory is completely out of the question.

Either way it seems this is the end of my contribution, because after re-uploading the code so many times I eventually broke the micro-USB port off my arduino, traces and all. So no more updates on my pendant. 😞

@dc42 thank you I ended up using this board for 2 signals ON and Reverse, and PWM to ananalog board for the RPM

@dc42 consider my request for canned cycles low priority then!

@theolodian see the M917 command. It works on all Duet 3 boards. The default standstill current is 71% of the running current.

@chrishamm My Bad I forgot to update the DWC and only updated the firmware. Thanks for the help.