@droftarts Wow, i feel stupid! I don't remember changing it but must have as it now loads. Thanks!

No activity for quite a while, but if anyone is still interested, here's a source of carbide cutter wheels. The V500 looks of particular interest, and they can manufacture to spec:

https://www.fletcher-terry.com/frame-joining-cutting-hanging-automation-1/carbide-cutting-wheels

I'm still using my original ground flanged steel bearing from 3+ years ago, and all is well

@wayneosdias try adding these lines to Config/SAMMYC21.h:

#define VARIABLE_NUM_DRIVERS 0 #define TMC22xx_HAS_MUX 0 #define TMC22xx_USE_SLAVEADDR 1

@T3P3Tony aaaand its back!

@tecno Put G92 Z0 A0 C0 D0 at the end of your homeall.g. You can create individual homez.g, homea.g, homec.g and homed.g if you prefer, with just G92 [axis]0 in them.

Ian

@droftarts ,

Thanks for your help. Here is what i have adjusted them to

M569 P0.0 S0 T2.5:2.5:2.5:2.5 ; 2.5us timings between pulses for X-axis M569 P0.1 S0 T2.5:2.5:2.5:2.5 ; 2.5us timings between pulses for Y-axis . . . M350 Z16 U16 V16 W16 A16 B16 C16 D16 'G16 I1 ; configure microstepping with interpolation. M92 X100.00 Y100.00 Z80.00 U80.00 V80.00 W8.888 A8.888 B8.888 C8.888 D8.888 'G8.888 ; set steps per mm . Ballscrew Pitch = 10mm/rev. M566 X900.0 Y900.0 Z900.0 U900.0 V900.0 W900.0 A900.0 B900.0 C900.0 D900.0 'G900.0 P1 ; set maximum instantaneous speed changes (mm/min) and use Jerk policy 1 M203 X51000 Y51000 Z6000 U6000 V6000 W3600000.00 A3600000.00 B3600000.00 C3600000.00 D3600000.00 'G3600000.00 ; set maximum speeds/feedrate (mm/min) M201 X5000.00 Y5000.00 Z2000.00 U2000.00 V2000.00 W180000.00 A180000.00 B180000.00 C180000.00 D180000.00 'G180000.00 ; set accelerations (mm/s^2) M906 Z1360.0 U1360.0 V1360.0 W560.0 A560.0 B560.0 C560.0 D560.0 'G560.0 I100 ; set motor currents (mA) and motor idle factor in per cent

As concerns Jerk , Duet measurement are in mm/min but openPnP are in mm/s^3

in order to convert that into mm/s^3 for OpenPnP do i just need to take Duet's config value and multiply by (60 * 1/S^3 )

i.e 900 mm/min = 900 x 60 mm/s =54000 mm/s x (1/s^2) = 54000 mm/s^3

is this correct assumption ? or Both Duet & OpenPnP must have be synchronized by having same Value ?

From this config is there anything you think might be a little out of place i.e Too high or too low

@wayneosdias said in M118 send hex values:

3.6 beta works, 3.5.3 doesn't. M260.2 only works on beta FW?

It says in the Gcode entry “Supported from firmware version 3.6”.

Ian

@Tinchus From my experience most of the resonance when it is speed specific will be related to any mass that is not perfectly centred on the ball screw (i.e how much of a banana the screw is). The motor will have its own resonance, but its exceedingly hard to mitigate that without straight up changing the type of motor.

Your right to think about changing the tip of the screw from a hard clamp to some form of plastic dampening clamp. it can still hold up the tip and provide a little bit of dampening enough to remove the resonance.

You can see a similar system used on the Prusa XL or our Construct1 XL printers 3485a756-eed9-4941-9a44-b3eb04eda352-image.png

(obviously these are threaded rods, but they work the same for ball screws)

Thanks for your answer.
So, the only way to control the extruder from outside it's sending commands via USB.
It's possible to do if I connect a SBC to the Duet3d or the situation is still the same?

@droftarts Thanks!

@NeelG I think you just missed M906 when you separated the extruder settings from the other axis settings. They are commented out here:

M906 X1500 Y0 Z1500 A1500 ;E1000:1000 ; set motor driver currents

Ian

@Sculpt-Fabricator sorry, wrong gcode. M563

@Alva The system staying in the printing state is to be expected when you get a motion error, it is basically partially shutdown when that error occurs. The question is why are you getting those errors. I assume if you just run whatever it is you are printing then you do not get that error. I'm not sure if running the second motion system from another gcode stream is causing a problem. From what I remember I think there may be some assumptions that both motion systems are running from the same gcode file (possibly forked using M606).

It might help if you post your config.g file and maybe a picture (or video) of your printer. I'm struggling to work out how all of this fits together, you seem to have two tools but six extruders and 5 axes. I'm also a little confused as to how the tools are controlled what moves when you command X and Y moves?