@dc42 also i found another bug with the help of a bad connection on heating cartridge:
i had a heater that got one wire disconnected, so i had teh gcode changing to the tool, waiting for it to heat thanks to the M116

and after maybe 30 seconds or one minute i saw the temp indicator turning purple (because it detects an error on the heating) but this didn't stopped the job, it just bypassed the M116 and so the tool change continue trying after that to performs cold extrusion.

and im' in stand alone mode.

@fcwilt ok thanks i will try that.

use this one to calibrate, it is specifically made for core xy calibration
https://www.thingiverse.com/thing:4018438

@arnold_r_clark honnestly i'm sorry to says that but @Kwad3D-0 wasn't cool at all, because for me too his sentence was not clear at all and could mean severall things. and instead of trying to rephrase he just choose to attack the guy that tried to helps him because HE knows.... but if HE knows better what's he's talking about why do he asks the question ??

when you asks for help it's sometimes VERY VERY usefull to just rephrase to explain to someone else that tries to helps you because it can either help the other people to know exactly what you are saying ( and not everyone is english native langage don't forget that) either it can simply makes you thing another way and see the things differently and find yourself a solution to your problem.

but honnestly if a guy gives me this answer:
"If I have to explain what that meant then you obviously are not going to be of much assistance"
i jsut want to answer him ok then go f*** yourself and don't waste our time.

and yes his sentence is crappy, the real one should be "the mesh generated got values that doesn't match the real position of the bed on the left (or right), they are offseted"

this sentence isn't ambiguous at all.
but he knows better and while people asked him (including @jay_s_uk who i think knows FAR FAR FAR better than him everything on how it works) to post his configuration, 5 days later he didn't.

but honnestly after looking this thread more deeply i jsut regret my post just above where i try to helps him because he's just toxic. jays reaction was the good one leave him with his problem as he don't really want an answer but just tell that RRF is crappy and makes him loosing money.

@paulhew yeah i thought he was toxic the second i saw there was two kwad3d
on the BLV FB page we had a same kind of guy complaining that he got a farm and things annoys him, and when we tried to explain to him he started be toxic. we explained him his behavior wasn't allowed and he quit the group of course not without telling we were just dumb guys that just play with toys while HE works. maybe he's the same guy

Hi,
i'm on reprapfirmware 3.5.4 on duet H6C with 3 expantion toolboard

my printer got 2 Z axis motors and unfortunately sometimes one of these two is not correctly aligned , even somtimes very skewed.

i may have up to 6-8mm of offset between the 2 sides of my bed.

i do have a auto leveling macro but as i put 3mm as S parameter for the M671

M671 X372:-62 Y160.9:160.9 S3

when i have too much skew the probe don't go until it hit the bed and i got this error message:

G30 P1 X17 Y140.9 Z-99999 S-1
Error: M280: Probe was not triggered during probing move

unfortunately the macro continue as if no error but the bed is not leveled at all.

my question is how can i get if the probe failed ?

i know i can retrieve the last probe value when it worked by using the model object variable

sensors.probes[0].lastStopHeight

this way if i'm able to retrieve the error then i'll be able to do raise only one side of my bed and retry to level it.

thanks for your help

damn that would be another reason for me to update my old duet2w from RRF2.1 to 3.3
no build another cnc first

@catalin_ro thanks, if the shipping costs where not that high i would go to teh queenbee pro, because it got interesting solutions about the rigidity on the X/Z axis.

On my side the flex is on torsion around the X axis, i mitigate a little by bolting both 2060 together but it's not enough.

i'll check on the z gantry around the Y axis as you mentionned to see if i have some.

0.05mm tolerance ? woaw, and i was quite happy with my 0.1mm.

i have to check if it changed or not but my machine is squared.
I had to replace the pulley because yes i had huge backlash because of that. But once again all parts came from ooznest, and if i have to redo them then i would probabley go to original gates belt and pulley to be sure.

i will try some pieces and yes i do have a smal square to check

thanks for the informations.

Re: [OOZNest WorkBee](screw driven)

@catalin_ro said in OOZNest WorkBee, screw driven:

After a lot of tests done with G2/G3, based on issues discovered while trying to machine a rather small Aluminum item, the maximum jerk should be limited to 300mm/min for X, Y and U. So change in config.g the line for M566 to:

M566 X300 Y300 Z12 U300

Hi @Catalin_RO Sorry to dig up such an old post but when i found this maybe you have the answer for me:

i have an OX CNC powered but duet 2 wifi clone and i'm quite happy with it i have mostly 0.1 to 0.3 max tolerance when milling aluminium which considering that the ox is far for rigid (especially the x grantry in torsion when plunging).

but every time i try to mill circles they are not exactly round, and it don't come from the material as i do have the same problem with a test milled with acetal.

when i check my circles, the diagonals radius are always 0.6mm bigger compared to the X or Y radius.

I just checked and my jerks (don't knwo why i have these values probably from the configurator) are set to

M566 X500 Y500 Z500               ; Set maximum instantaneous speed changes (mm/min)

would that explain my circles no so round ?

oh and i just checked on the gcode generated as i use ramps for plunging i have both succession of G1 and G2 used, here is an eaxmple for one depth (got 5 other layers like this one)

; MOVEMENT_RAMP
G1 X55.535 Y28.094 Z1.984 F400
G1 X55.158 Y27.84 Z1.968
G1 X54.776 Y27.593 Z1.952
G1 X54.391 Y27.352 Z1.937
G1 X54.001 Y27.119 Z1.921
G1 X53.607 Y26.891 Z1.905
G1 X53.21 Y26.671 Z1.889
G1 X52.808 Y26.457 Z1.873
G1 X52.404 Y26.251 Z1.857
G1 X51.995 Y26.051 Z1.841
G1 X51.584 Y25.858 Z1.825
G1 X51.169 Y25.673 Z1.81
G1 X50.751 Y25.494 Z1.794
G1 X50.33 Y25.323 Z1.778
G1 X49.906 Y25.159 Z1.762
G1 X49.479 Y25.002 Z1.746
G1 X49.05 Y24.853 Z1.73
G1 X48.618 Y24.71 Z1.714
G1 X48.184 Y24.576 Z1.698
G1 X47.748 Y24.449 Z1.683
G1 X47.309 Y24.329 Z1.667
G1 X46.869 Y24.217 Z1.651
G1 X46.426 Y24.112 Z1.635
G1 X45.982 Y24.015 Z1.619
G1 X45.537 Y23.925 Z1.603
G1 X45.09 Y23.844 Z1.587
G1 X44.641 Y23.769 Z1.571
G1 X44.191 Y23.703 Z1.556
G1 X43.741 Y23.644 Z1.54
G1 X43.289 Y23.593 Z1.524
G1 X42.837 Y23.55 Z1.508
G1 X42.383 Y23.514 Z1.492
G1 X41.93 Y23.487 Z1.476
G1 X41.476 Y23.467 Z1.46
G1 X41.021 Y23.454 Z1.444
G1 X40.567 Y23.45 Z1.429
G1 X40.112 Y23.453 Z1.413
G1 X39.658 Y23.464 Z1.397
G1 X39.204 Y23.483 Z1.381
G1 X38.75 Y23.51 Z1.365
G1 X38.297 Y23.544 Z1.349
G1 X37.844 Y23.587 Z1.333
G1 X37.392 Y23.637 Z1.317
G1 X36.941 Y23.694 Z1.302
G1 X36.492 Y23.76 Z1.286
G1 X36.043 Y23.833 Z1.27
G1 X35.596 Y23.913 Z1.254
G1 X35.15 Y24.002 Z1.238
G1 X34.706 Y24.098 Z1.222
G1 X34.263 Y24.201 Z1.206
G1 X33.822 Y24.313 Z1.19
G1 X33.383 Y24.431 Z1.175
G1 X32.947 Y24.557 Z1.159
G1 X32.512 Y24.691 Z1.143
G1 X32.08 Y24.832 Z1.127
G1 X31.651 Y24.98 Z1.111
G1 X31.224 Y25.136 Z1.095
G1 X30.799 Y25.299 Z1.079
G1 X30.378 Y25.47 Z1.063
G1 X29.959 Y25.647 Z1.048
G1 X29.544 Y25.832 Z1.032
G1 X29.132 Y26.023 Z1.016
G1 X28.723 Y26.222 Z1
; MOVEMENT_FINISH_CUTTING
G2 X14.521 Y55.31 I11.811 J23.778 F825
G2 X16.04 Y56.55 I1.519 J-0.31
G1 X65.03
G2 X66.548 Y55.31 J-1.55
G2 X28.723 Y26.222 I-26.014 J-5.31

thanks

@dc42 is this restore behavior only for a code that is on the macro folder or is it the same if my code is in sys folder ?

thanks

@dc42 oh ok so i really have to check about that because i was counting on the fact that some macro set absolute coordinates.
thx

@fcwilt ok thanks i will try that.

I have a macro that i call from my gcode.

some of my slicers autogenerate the gcode from some parameters (calibration tests mostly) but they are working in relative mode.

what i want to do is on my macro check if i'm in relative or absolute coordinate mode, change to absolute, do the code of the macro
and then set back to absolute or relative according to the value i read at the beginning of my macro.

thanks

@dang472 maybe the easiest for you is to use a toolboard v1.1 as it got an integrated accelerometer.

@hayden1993 i think that maybe if it's your first CNC with a duet, you should try with limit switches (this is what i have and i don't have to complain with the repetability),
and then once you're familiar with everything you can change the limit switches with either optical or other sensors. and for the limit switches it's really easier to use reprap ones:
https://aus3d.com.au/endstop-pcb
because they have a led that helps you know the wires are correctly connected and you see the trigger.