Topics created by psychotik2k3

@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.

@psychotik2k3 it is for all macros. When any macro starts executing, various parameters are saved and then restored when the macro finishes or aborts. The list of these parameters includes the relative/absolute axis movement flag, the relative/absolute extrusion flag, the feed rate, the inches/mm flag, and the plane selected for arc moves.

@psychotik2k3 An alternative approach is to modify your bed.g to have two stages. An initial stage probes the bed only along a short line between your two bed mount points/motor locations and allows for larger corrections than 3mm. The second stage uses your existing bed levelling points. The idea is to allow the initial correction to get the bed roughly level with no danger of crashing part of the hot end/probe into the bed if the bed is really at an angle. So basically you probe the bed at the centre to get a zero/home point then probe at two points either side of that towards your motors but not that far from the centre of the bed (so that movement of the head is still safe with a heavily skewed bed), this then provides a crude correction. Then rehome Z in the centre of the bed and continue with the more accurate (but smaller) bed correction taken at points near to your motor mounts.

I've been using something similar to this for a long time and it works very well for me, my bed has a habit of dropping a fair bit when the motors are not powered, but only on one side and this procedure handles this very well without manual intervention.

@dc42 stand alone

@dc42 couldn't test as i performed some long prints. but yes it works.
thanks for your hard work.

@dc42 thanks

@dc42 yes here they are:

06/06/2021, 21:55:19 M122 B0 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3RC3+4 (2021-06-05 16:20:17) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956BA-NA3TN-6JTD8-3S86J-1UB2T Used output buffers: 3 of 40 (40 max) === RTOS === Static ram: 150896 Dynamic ram: 93488 of which 112 recycled Never used RAM 106840, free system stack 152 words Tasks: NETWORK(ready,28.3%,234) ETHERNET(notifyWait,0.1%,124) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,284) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,340) TMC(notifyWait,7.7%,59) MAIN(running,63.7%,924) IDLE(ready,0.2%,29), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:01:03 ago, cause: power up Last software reset at 2021-06-06 21:54, reason: MemoryProtectionFault mmarValid daccViol, none spinning, available RAM 109912, slot 1 Software reset code 0x4172 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00c00804 BFAR 0xdcfffff5 SP 0x2041fcc8 Task NETW Freestk 569 ok Stack: 2043a6a0 00000001 20418194 00000001 00000000 0047a76f 004239ba 210f0000 a5a5a5a5 0047a88b 00000001 2041fd08 0092dc03 004781bd 204299d0 0041fb41 2041f070 3f1e9901 37533333 43d697a0 00000000 ffffdbb1 fdcbaeaf fffefc23 ffffffff ffffffff ffffffff Error status: 0x04 Aux0 errors 0,4,0 Step timer max interval 129 MCU temperature: min 38.4, current 41.9, max 42.0 Supply voltage: min 23.4, current 23.7, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0 Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/40/40, gc cycles 0 Driver 0: position 58520, standstill, reads 24588, writes 18 timeouts 0, SG min/max 0/186 Driver 1: position -12600, standstill, reads 24588, writes 18 timeouts 0, SG min/max 0/191 Driver 2: position 5592, standstill, reads 24588, writes 18 timeouts 0, SG min/max 0/181 Driver 3: position 0, standstill, reads 24588, writes 18 timeouts 0, SG min/max 0/161 Driver 4: position 0, standstill, reads 24596, writes 11 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 24596, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2021-06-06 21:55:18 Slowest loop: 7.66ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.1ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 9505ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 16, completed moves 16, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 3 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP is ready with "M122 B0" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 618, send timeouts 0, received 800, lost 0, longest wait 1ms for reply type 6042, peak Tx sync delay 182, free buffers 49 (min 48), ts 318/317/0 === Network === Slowest loop: 4.19ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 1 0 0 Socket states: 5 2 2 2 2 0 0 0 06/06/2021, 21:55:21 M122 B1 Diagnostics for board 1: Duet EXP3HC firmware version 3.3RC3+1 (2021-05-29 10:22:51) Bootloader ID: not available Never used RAM 158144, free system stack 4400 words Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,113) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,83) CanClock(notifyWait,0.0%,74) TMC(notifyWait,22.8%,63) MAIN(running,75.7%,303) IDLE(ready,0.0%,40) AIN(delaying,1.4%,263), total 100.0% Last reset 00:01:05 ago, cause: power up Last software reset time unknown, reason: AssertionFailed, available RAM 159320, slot 0 Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x20004754 Task HEAT Freestk 142 bad marker Stack: 00000544 0002ebf8 000261ef 42000400 00022423 2002f020 00000000 2002f038 2000151c 00000000 0001d6c1 0002dde4 0002de9c 0002d4a0 00025035 2000159c 00000000 2002f020 00015609 00000000 000009c4 000009c4 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00025035 Driver 0: position 0, 424.9 steps/mm, standstill, reads 53827, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0 Driver 1: position 0, 917.4 steps/mm, standstill, reads 53829, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0 Driver 2: position 0, 406.0 steps/mm, standstill, reads 53833, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 0/7, peak Rx sync delay 178, resyncs 0/0, no step interrupt scheduled VIN: 23.8V, V12: 12.2V MCU temperature: min 36.2C, current 36.7C, max 36.7C Ticks since heat task active 201, ADC conversions started 66031, completed 66030, timed out 0, errs 0 Last sensors broadcast 0x0000000e found 3 206 ticks ago, loop time 0 CAN messages queued 859, send timeouts 0, received 646, lost 0, free buffers 37, min 37, error reg 110000 dup 0, oos 0/0/0/0, bm 0, wbm 0

@psychotik2k3 oh and my Z home is this:

G1 X 175 Y 175 F6000 M558 F250 ; Set the probing speed G30 M558 F30 ; Set the probing speed G30

and my probe offset in config.g

G31 P500 X32.5 Y67.5 Z3.75 ; for BLTouch

@phaedrux yes you're right gpio is extended and power seems to go the GPIO too.
just tried to set the jumper in allways on mode so i bypass the swithc but it d'ont change anything. send a mail to argon to ask why i have this behaviour.

@psychotik2k3 Not before version 3.3 but in the meantime you can already use slots to store positions and to restore them. See G60 and G1 R. If you need to use stored positions with other codes, you can access them via the object model as well. They're exposed by state.restorePoints[].coords[].

Does not work for me on RRF3.01_RC1 with duet3 board with SBC and bed levelling with independent Z motors (G32) no longer reports the deviations!

Please try this with firmware 2.04RC1 and report whether the behaviour is the same.

@bearer said in add an H4 parameter to G0/G1 for just halt when endstop is hit ?:

@Danal said in add an H4 parameter to G0/G1 for just halt when endstop is hit ?:

(Not asking about Work Coords, or etc. got all that, just asking about how, physically, to probe when Z0 = bottom of stock / top of spoil.)

But if you use work coordinates with known tool lengths you don't have to probe (if the setup is rigid enough). Just set the work coordinates after facing the spoil board.

Agreed! Same thing. The tool face has set the Z0, whether by facing or probing, it is still the lowest point of the tool.

At the same time, this assumes both "no tool wear" and "tool lengths are at least as accurate as probing". Could be true that neither make enough difference to worry about in given setups. For example, much commercial CNC repetitive work chooses to operate this way, and it works great.

Could be true, as in my case with collets but no tool holders, that "known tool lengths" is a non-starter. Probing (or some form of "touching off") at tool change, including start-of-cut, is the only choice. Preserving Z0 from facing the Martyr/Spoil is literally impossible (assuming the stock is cut with a different bit than was used to face the spoil).

@dc42 In theory it should make a difference because as I keep saying, at 16x with single digit mixing ratios the extruder move could be in the region of 1/10th of a micro step or less. The only question remains is whether a single 1/256 micro step translates to any physical movement of the motor/filament. If not, what does. Is 128x, 64x or what? One of these days I'll run some more tests. I know exactly the colour combination to use. It's White and Red. The tiniest amount of red leads to pink. So a cylinder with 0.5mm segment sizes using single digit mixing of red with white would be the part to print. Five copies, at 16x, 32x, 64x, 128x and 256x. Maybe print them in vase mode. (Note to self, add this to the "todo" list).