@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

@nurooi use a 100mm cube, 1 bottom layer, 1 perimeters, and no infill. the Script will called on layer change in the slicer

@peter247 yes it is

@chrishamm My SBC is running the full DuetPi image. My workstation is running Windows 10. I can test from my laptop I suppose.

FYI Firmware 3.3 RC 3 did not fix the issue.

@phaedrux The last week i had no issues with 3.2.2 so i will try today to go to the latest beta and try to get this problem

@chernogorsky it should still work in standalone mode, but it has never worked in SBC mode.

I confirm this is fixed in 3.3RC3.

@krohm-koala said in [3.3.0-rc2] M3-M5 gcode action:

hen you want to adjust your focus, it's a bit difficult duri

Does your laser have a Z-axis to adjust height? I'm planning for mine too - so eventually I'll do a test g-code that fine adjusts the laser height over multiple passes, and to than workout the offset from the top of the material being engraved/cut.

Interesting. Glad you got it sorted. I guess in future I'll have to remember if in doubt, delete the map and try again.

@dc42 Great, thanks for confirming that, I'll work on switching over.

@Nuramori flagging you so you see this - from my understanding of your logs, I think you're running in SBC mode as well.

@boa, I left my machine on for 9 hours with io3.in connected to ground, and I didn't see any false triggers. So I am fairly sure that the issues you are seeing are caused by noise pickup or that the sensor is generally producing spurious triggers. It may be that RRF 3.3 response to noise pulses faster than previous versions, because the loop that polls the triggers is no longer responsible for managing motion, so it may execute faster.

If the sensor cable run close to a stepper motor cable, and the false triggers only occur when that stepper motor is energised, then it may be that the sensor cable is picking up inductive interference from the stepper motor cable.

@argo thanks for confirming this.

@dc42
@Argo
I've tested the new firmware and it's ok. No bug with M291. The print was well paused during all the process.
Thank you very much !

@jbarros thanks for confirming.

@stewwy I've added this to the work list for RRF 3.4.

@jay_s_uk I can see why that won't work. The firmware models the bed as a plate that can have an XY twist. With four mounting points positioned at the centres of the edges, three of them would define the bed plane and adjustment of the fourth one would bend the bed instead of twisting it. So the matrix used in the calculation is singular.

@chrishamm

made the changes you suggested, and it is getting it to a working state. there still seem to be a noticeable delay that changes from probe to probe. but none of them are long enough to error out the BLtouch.

so its working, but not sure if it behaving as intended. but maybe as good as it gonna get on a pretty unusual config.

@siam Thanks, I can confirm the highlighted item is off once the file list changes. I've got a fix ready for this.