I wanted to try installing again same firmware and updates before maybe going to RRF3.
No idea why, but it has solved my issue.

Thank you for your answers and time.

That's why it's referred to as Idle Hold. The motors aren't doing hard work, so they don't need a lot of current, but they still need enough to hold position. Reducing the current lets them cool down.

M906 I sets the percentage of full current, and M84 S sets the amount of time to wait before considering the motors idle. Usually 30 seconds or so of inactivity.

A lot can be learned by looking up each gcode in the wiki to see what it does and how it works.

https://duet3d.dozuki.com/Wiki/Gcode#main

@Phaedrux I've been trying to configure in the RRF configuration tool but I get stuck in missing one of the stepper motor drivers.. Not sure how to add the "ghost driver" or how one would call it, the one on the other side that copies the other one exactly. (yes I'm that new)

I was playing with this for a lathe and did not find a proper solution with stepper

using a stepper shown to be crap for the spindle, I even tried large nema34 16A ones... the torque & speed are just not acceptable, even with FPGA stepper (mesa card and linuxcnc, so I was easily stepping at 2MHz but it's just not something stepper deals with) using encoder and servo worked great on linuxcnc + mesa but I never managed to reproduce this on any of the 32bit boards (rrf, redeem, smoothie..), especially as there's no way to push encoder data back into them... also stepping speed on all of them is too slow for high precision encoder on the servo ..

I do have a small mill where I use smoothieware (RRF would work even better maybe) where I control the spindle by SPI, I have a small pic that listen to SPI and it gets the speed for the spindle from SPI from the firmware and then it converts it to 1-10V input for the VFD ... (I lost that firmware for the pic 😞 but it's a 30min job to write for any mcu, I need to write it again I need another one for a bit different mini mill I have)

I'm back to post the probe macros as stated above. I kind of got lost trying to do all axes in one macro and ran into trouble with the the offset, end-mill radius, saving and restoring a tool position with the G60 command, DWC workstation coords were not making sense, and I couldn't figure out why the G38.2 only ran in a negative direction on some macros, etc... Then applied the tried and true K.I.S.S. technique and then the DWC showed me zeros on all axes at the workpiece origin. Yeah baby!

The macros below are a jog to an axis position before you start the probe macro. This should be a easy start for all of us CNC noobs out there trying to get started cutting some material and making stuff.

The macros are simple straight forward easy to edit starting point. When your are ready to make a "do-all axes at once" macro, I found that calling each separate axis macro within a single macro with the M98 command the best way to prevent an error message from the DWC stating that the probe was already triggered after probing the first axis in the code.

I hope this helps to get you started.

Jog-Q-X-Probe.g The Q stands for a 1/4 (quarter) inch end-mill. The macro needs to be edited for 1/8 or any other size.

; Jog-Q-X-Probe.g - Quarter (6.4mm) end-mill X Probe, jog tool in position to touch plate B4 starting this macro ; For use with Openbuilds XYZ Touch Probe Plus (10mm edge thickness, 9mm top thickness). ; G21 ; Metric G38.2 X-50 F100 ; Seek along X until contact with probe plate G10 L20 P1 X13.2 ; Store probe offset's in co-ordinates system for X G91 G1 X5 F300 ; Back away from touch plate G91 G0 Z15 ; Move Z quickly up

Jog-Q-Y-Probe.g

; Jog-Q-Y-Probe.g - Quarter (6.4mm) end-mill Y Probe, jog tool in position to touch plate B4 starting this macro ; For use with Openbuilds XYZ Touch Probe Plus (10mm edge thickness, 9mm top thickness). ; G21 ; Metric G38.2 Y50 F100 ; Seek along Y until contact with probe plate G10 L20 P1 Y-13.2 ; Store probe offset's in co-ordinates system for Y G91 G1 Y-5 F300 ; Back away from touch plate G91 G0 Z15 ; Move Z quickly up

Jog-Q-Z-Probe.g

; Jog-Q-Z-Probe.g - Quarter (6.4mm) endmill Z Probe, jog tool in position to touch plate B4 starting this macro ; For use with Openbuilds XYZ Touch Probe Plus (10mm edge thickness, 9mm top thickness). ; G21 ; Metric G38.2 Z-50 F100 ; Seek along Z until contact with probe plate G10 L20 P1 Z9 ; Store probe offset's in co-ordinates system for Y G91 G1 Z5 F300 ; Back away from touch plate

XYZ-Probe.g This is an example of how to use the M98 gcode command to run a set of macros using the Openbuilds touch probe plus. The touch plate has a 14mm hole at the X0, Y0, Z0 coords of the touch plate that can be used as a start and end point for each individual axis macro so you can call them all in a single macro. When I tried to run a macro that triggered the probe more than once I received an error from the DWC. I am not sure if the error was significant enough to cause the a problem with the coordinate system since I abandoned the hack for the M98.

; Calls all macros for quarter size bits on all axes M98 P"/macros/XY-Probe-center.g" ; run XY-Probe-center.g from Macros directory in the DWC G4 S1 ; dwell (pause) for 1 sec M98 P"/macros/Z-Probe.g" ; run Z-Probe.g from Macros directory in the DWC G4 S1 ; dwell (pause) for 1 sec M98 P"/macros/Y-Probe.g" ; run Y-Probe.g from Macros directory in the DWC G4 S1 ; dwell (pause) for 1 sec M98 P"/macros/X-Probe.g" ; run X-Probe.g from Macros directory in the DWC

@perigonza said in Weird G-Code needed on my duet maestro wifi!:

that was my first lecture but didn't help solve the problem

That's odd, because I'm quite sure both mention using M452 for laser mode.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M452_Select_Laser_DeviceMode

PS - you can also recall the workplace coordinates, you will find them within move.axes[n].

I got it sorted. I was missing the WCS, and G55 commands.

Yes Christian confirmed, I did email him to see weather his developing a workaround but he's not got back to me yet.

I think Oozenest have a relationship with Vectric so probably tricky for them to recommend another platform.

As it seems a bit vague which software (outside of Fusion and Ventric) will work with Duet, I might buy an Arduino system for the short term and use that to make life easier while I'm starting out.

@T3P3Tony excellent! thank you very much!

@kazolar said in VFD integration: M3, M4, M5 Macros and RPM measurement:

@dc42 just found that you added the pin assignments -- will definitely try that out -- any thought to the dwell time option -- the dwell would apply to M3, M4, M5 -- do the task, then wait dwell time to move to next line. Basically combining M# with G4. Also if M6 just runs a macro, that would also be really useful. I added that in my code since I added a tool height probe, so M6 runs a macro to doing an assisted toolchange with a tool height probe.

Yes, adding a dwell time in seconds would be the icing on the cake...

@oribotic if the error follows the motor that would definitely indicate a wiring issue

@dc42 I think M585 does it -- I just tried it -- and it looks like it set my offset correctly. Will make a rigid mount for my button and do more tests.

Well, this was a unique learning experience. I moved the homing files to the "Macros" under the "File Management" a month ago, while dealing with the firmware issue.

I moved them back to the "System" section in the "File Management" menu in the DWC. All is back to normal, if there is such a thing...

Thanks for your help.

@maxspongebob said in Obey hard limit switches?:

Requiring that the customer also create and program macros to achieve basic functionality is a stretch.

Really? Given the amount of work that goes into building these machines a few minutes coding a macro is a stretch?

Frederick

@Phaedrux said in Duet 2 Wifi power supply requirements:

Instructions unclear. DuetWifi currently sparking in microwave. Please advise.

Full power or defrost?!

Ian

@bearer I’m not too certain what the other options are. There is that black box that open builds sells. And there are some other things that run Mach4 on Amazon.

Did you correct your M675?

I'm not sure I understand what you mean.

If M3/4 ran macros m3.g/m4.g then this machine specific behaviour could be programmed in g-code for each machine?