In RRF 3.01 and later, if a P parameter is provided then only the retraction parameters for the specified tool will be set. says : https://duet3d.dozuki.com/Wiki/Gcode#Section_M207_Set_retract_length

@dc42 what purpose hardware reset pin is for?

@ctilley79 My BL-Touch used to go in blink state too ,So I've this line to change its mode to ALARM RELEASE in my config at the end and even at start and end of bed.g . Try this I suppose.
For deployment problem I would suggest you to increase dive height that is H parameter's value in M558 which is 3 right now. Mine is 8.

@fcwilt said in Question about bed probing:

so why not just continue the process and level it?

wanted to make it less human dependent .
No biggie... I'll go with current method .

Thanks for the help

@resh can you do following:
home any one axis. Manually light up respective endstop and see if axis actually stops immediately (Don't wait for it to reach to endstop).

If it doesn't stop then manually light up endstops of other axes and see if it stops .If so you have configured them wrongly. But if it doesn't stop at all then there might be wiring issue I guess.

@dc42 I have faced a similar issue , when upgraded from 3.3beta Feb1 release to to RRF 3.3.0.
Axes X-Y are connected on EXP1XDs and I have end-limits on both the low and high ends. After upgrade, Axes started hitting the end-limits on the other(high) ends . I suppose It is the same issue as of @marco-bona & due to incorrect homing, axes hit the endstops.

NOTE: After downgrading to previous release i.e. (3.3beta Feb1) , problem is gone.

Do you concur the issues are similar?

@dc42 Doing so is generating:

I don't see any .elf generated ? what am I supposed to do with these generated files to get .bin?

Dear @oliof @deckingman
I believe there is a grave misunderstanding here!

Please be rest assured, that I have not done anything that contradicts the licensing terms. The very first question in the thread was "Can I ....?" .
I am aware of GNU license terms and have adhered to it, being an active forum user, i also solve queries possible. However, It was a requirement from a naive user who doesn't know how to code and hence the question. Intention here was just to see if user requirement can be fulfilled and nothing more!
I guess the subject was misleading and fixed hence!

NOTE: my version of DWC = DWC with dark theme with some colors changed for user. no breaching of license.

I will check with Chris Hamm , if a solution can be derived to this kind of user requirement.

@phaedrux Yes, We have done this calibration.

Please refer above image.

When I measured maximum value above my set tolerance. I again modify that value above the measured value. then I give print and I got bigger value then I have set that tolerance.
For example: I have measured R maximum 2600 (using M591 D0) then, I set R value maximum 3000 (M951 D0 R20:3000) and give print and print pause due to too much movement and I got measured value 3200 (using M591 D0).

Can you give advice for the problem?

@phaedrux
We are using below listed BTT sensor:
https://www.ubuy.co.in/product/D6I7DZS-bigtreetech-smart-filament-sensor-filament-break-detection-module-3d-printer-parts-for-1-75mm-filame/s/bigtreetech-smart-filament-sensor-filament-break-detection-module-3d-printer-parts-for-1-75mm-filament-skr-v1-3-mini-e3-gen-v1-4?utm_source=gad&utm_medium=cpc&utm_campaign=inshop&loc=9062189&gclid=EAIaIQobChMIpNLd7eLn9AIVlnZgCh1z5wPfEAYYAiABEgKlkPD_BwE

We are trying to calibrate sensor but value for range is changing every time.
minimum value and maximum value set by R30:350
When we add 350 maximum value and after giving print, We observe print stop due to too much movement and value shown above 350. it happens every time.
Can you explain about R and E parameter in M591 D0 P7 C"^e0stop" L7 R30:350 E17 S1
Is there any combination for R and E value??

My setting for BTT Filament sensor:
M591 D0 P7 C"^e0stop" L7 R30:350 E17 S1
Issue: I got too much movement error frequently and print pauses.
After that I have changed
M591 D0 P7 C"^e0stop" L7 R30:350 E20 S1
Now error come up less frequently compared to previous setting.
Can you explain the term "L7 R30:350 E20 S1"
and
What should I do for removing error permanently? @Phaedrux

@T3P3Tony I had checked with older firmware and same result. I know there is no issue with software and G-code. I think it's related to backlash. Is there any possible solution?

@dc42 Any suggestions to resolve this backlash problem in preloaded ball screw system.

I am using Latest RRF3.4beta3. This is a first time I am facing such wall gap issue. my machine has 2 Y Axis motor and 1 X axis motor. All the problems are coming in when the both axes motors running together, specifically from top left top to bottom right direction or vice versa( i.e. from right bottom to left top).

@jay_s_uk I see no hiccups.
B40 -> 1XD of X-axis | B41 -> for Y

18/08/2021, 14:41:45 M122 B41
Diagnostics for board 41:
Duet EXP1XD firmware version 3.4.0beta2 (2021-08-03 10:00:36)
Bootloader ID: SAMC21 bootloader version 2.0 (2020-10-15b1)
Never used RAM 5520, free system stack 2743 words
Tasks: Move(notifyWait,0.1%,111) HEAT(delaying,0.1%,111) CanAsync(notifyWait,0.0%,60) CanRecv(notifyWait,0.1%,75) CanClock(notifyWait,0.1%,64) MAIN(running,82.8%,443) IDLE(ready,0.0%,41) AIN(notifyWait,16.9%,142), total 100.0%
Last reset 04:03:05 ago, cause: power up
Last software reset data not available
Driver 0: position -338478, 400.0 steps/mm, steps req 31734448 done 31492466
Moves scheduled 6014, completed 6014, in progress 0, hiccups 0, step errors 0, maxPrep 713, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 5/10, peak Rx sync delay 203, resyncs 0/0, no step interrupt scheduled
VIN: 24.5V
MCU temperature: min 29.8C, current 36.1C, max 36.5C
Ticks since heat task active 191, ADC conversions started 7292707, completed 7292707, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 196 ticks ago, loop time 0
CAN messages queued 39, send timeouts 0, received 137302, lost 0, free buffers 37, min 36, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 337, adv 35378/74655

18/08/2021, 14:41:43 M122 B40
Diagnostics for board 40:
Duet EXP1XD firmware version 3.4.0beta2 (2021-08-03 10:00:36)
Bootloader ID: SAMC21 bootloader version 2.0 (2020-10-15b1)
Never used RAM 5520, free system stack 2743 words
Tasks: Move(notifyWait,0.1%,111) HEAT(delaying,0.1%,111) CanAsync(notifyWait,0.0%,60) CanRecv(notifyWait,0.1%,75) CanClock(notifyWait,0.1%,64) MAIN(running,83.2%,438) IDLE(ready,0.0%,41) AIN(delaying,16.5%,142), total 100.0%
Last reset 04:03:03 ago, cause: power up
Last software reset data not available
Driver 0: position -216541, 400.0 steps/mm, steps req 11854527 done 11614529
Moves scheduled 5014, completed 5014, in progress 0, hiccups 0, step errors 0, maxPrep 697, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 5/10, peak Rx sync delay 198, resyncs 0/0, no step interrupt scheduled
VIN: 24.3V
MCU temperature: min 29.2C, current 36.5C, max 36.7C
Ticks since heat task active 206, ADC conversions started 7291589, completed 7291589, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 212 ticks ago, loop time 0
CAN messages queued 38, send timeouts 0, received 136282, lost 0, free buffers 37, min 36, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 468, adv 35268/74637

18/08/2021, 14:41:40 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta2 (2021-08-03 12:42:33) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J9D4-3S86J-TA36F
Used output buffers: 8 of 40 (40 max)
=== RTOS ===
Static ram: 151128
Dynamic ram: 93712 of which 0 recycled
Never used RAM 102592, free system stack 142 words
Tasks: NETWORK(ready,117.1%,236) ETHERNET(notifyWait,0.0%,176) HEAT(delaying,0.1%,326) Move(notifyWait,0.5%,250) CanReceiv(notifyWait,0.0%,821) CanSender(notifyWait,0.0%,361) CanClock(delaying,0.0%,340) TMC(notifyWait,42.9%,59) MAIN(running,122.6%,1114) IDLE(ready,0.0%,29), total 283.2%
Owned mutexes:
=== Platform ===
Last reset 04:02:58 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 109284, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 131
MCU temperature: min 26.6, current 41.5, max 41.7
Supply voltage: min 23.7, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.3, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/32/20, gc cycles 0
Driver 0: position 23459, standstill, reads 35346, writes 11 timeouts 0, SG min/max 0/0
Driver 1: position 23522, standstill, reads 35346, writes 11 timeouts 0, SG min/max 0/0
Driver 2: position 640, standstill, reads 35341, writes 17 timeouts 0, SG min/max 0/398
Driver 3: position 0, standstill, reads 35341, writes 17 timeouts 0, SG min/max 0/415
Driver 4: position 0, standstill, reads 35342, writes 17 timeouts 0, SG min/max 0/203
Driver 5: position 0, standstill, reads 35351, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-08-18 14:41:39
Slowest loop: 111.25ms; fastest: 0.05ms
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.6ms, write time 24.1ms, max retries 0
=== Move ===
DMs created 125, segments created 16, maxWait 225523ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 6856, completed moves 6856, hiccups 0, stepErrors 0, LaErrors 0, Underruns [1, 0, 4], 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 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X59.068 Y58.375 E17.1829" 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
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 142271, received 33, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 186, free buffers 49 (min 41), ts 72894/72893/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 34.28ms; 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 0 0 0
  Socket states: 5 2 2 2 2 0 0 0

@phaedrux for me 3.3 beta Feb 1 release works perfectly. Versions other than that are causing the same issue!! I've downgraded it to 3.3bFeb1 for time being.

After upgrading boards i.e. Main board ( Duet3 MB6HC ) and EXP1XDs to RRF - 3.4beta2 , motors started to hang randomly during prints . I have my axes X and Y , connected to EXP1XDs . Z and Extruder on Duet3. I was printing at speed 50 and observed hangs on random turns. On resume , it resumes correctly . What do I do ? Please help!

As I couldn't find Duet3Firmware_EXP1XD.bin
with main bin, I only upgraded main board and kept my 1XDs on 3.3beta. I received warning : Discarded std reply src... after upgrading main board to 3.4b1. So I searched and found : https://forum.duet3d.com/topic/23872/warning-discarded-std-reply . It is same with me. Where can I get corresponding bin for EXP1XD from ?