• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

BL Probe deploys when Scanning Z probe cycles run

Scheduled Pinned Locked Moved Solved
Duet Hardware and wiring
4
7
261
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    Invader_Zoom
    last edited by 4 Aug 2024, 15:38

    Hello all,
    I'm looking for some assistance setting up my Scanning Z Probe. The trouble comes when attempting to run the M558.1 calibration. The calibration runs successfully; however, the BL touch probe deploys at the same time and leaves the BL probe in error status at completion of the calibration routine. This behavior persists despite specifying the K1 parameter with M558.1 (M558.1 K1 S1.5 example command) where the BL is configured as K0 and the SZP as K1. Similarly, when running the bed mesh (G29 K1) the BL probe deploys which will damage the probe as the pin drags across the bed.

    While I could write a reset for the BL probe into a macro for M558.1 to solve the first issue I'm not aware of how I could similarly edit the G29 routine and this doesn't really address the root issue.

    Any thoughts or advice is appreciated.

    Firmware 3.5.2

    Hardware is as follows;
    Controller: Fysetc Big Dipper (mimics Duet Mini 3 5+)
    Toolboard: Mellow Fly RRF address 124
    Probes: Genuine BL Touch, Duet SZP (address 120)

    Config file and M122 outputs:

    M586 P0 S1 ; enable HTTP
    M586 P1 S0 ; disable FTP
    M586 P2 S0 ; disable Telnet

    G4 S1 ;WAIT FOR TOOLBOARD CONNECTION

    ; Drives
    M569 P0 S0 ; physical drive 0.0 goes forwards
    M569 P1 S0 ; physical drive 0.1 goes forwards
    M569 P2 S0 ; physical drive 0.2 goes REVERSE
    M569 P3 S0 ;"
    M569 P4 S0 ;"

    M569 P124.0 S1 ; physical drive 121.0 goes forwards
    M584 X0 Y1 Z2:3:4 E124.0 ; set drive mapping
    M671 X-68:290:650 Y 10:650:10 S150 ;SET LEADSCREW LOCATION FOR COMPENSATION
    M350 Z16 I0 ; configure microstepping without interpolation
    M350 X16 Y16 e16 I1 ; configure microstepping with interpolation
    M92 X81.08 Y81.08 Z1600 E690.00 ; set steps per mm
    M566 X1750 Y1250 Z26.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X20000.00 Y20000.00 Z2500.00 E7000.00 ; set maximum speeds (mm/min)
    M201 X3200.00 Y3000.00 Z400.00 E8000.00 ; set accelerations (mm/s^2)
    M906 X1550 Y1550 Z1350 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent ;X1400 Y1400 Z1000 E1000 I30
    M84 S30 ; Set idle timeout

    ; Axis Limits
    M208 X0 Y0 Z0 S1 ; set axis minima
    M208 X605 Y561 Z255 S0 ; set axis maxima

    ; Endstops
    M574 X1 S1 P"124.io2.in" ; configure active-high endstop for low end on X via pin io0.in
    M574 Y1 S1 P"io0.in" ; configure active-high endstop for low end on Y via pin io1.in
    ;M574 Z2 S1 ; configure Z-probe endstop for high end on Z

    ; Z-Probe
    M950 S0 C"124.io0.out" ; create servo pin 0 for BLTouch
    M558 k0 P9 C"^124.io0.in" H15 F120 T10000 R0.2 ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X26 Y-8.5 Z2.58 ; set Z probe trigger value, offset and trigger height
    ;M557 X20:600 Y15:600 S40 ; define mesh grid

    M280 P0 S60 ; BLtouch - toggle switch mode
    G4 P1000 ; wait 1 second
    M280 P0 S120 ; BLtouch toggle self-test

    ; Scanning Z probe
    M558 K1 P11 C"120.i2c.ldc1612" F36000 T36000 ; configure SZP as probe 1, type 11, on CAN address 120
    M308 A"SZP coil" S10 Y"thermistor" P"120.temp0" ; thermistor on SZP coil
    G31 K1 Z2 Y-17 ; define probe 1 offsets and trigger height

    m558.2 k1 S15 R137084

    M557 X50:200 Y50:250 S10 ; Define mesh grid for probe 1 (overwrites probe 0 mesh grid)

    ; Heaters
    M308 S0 P"temp1" Y"thermistor" T120000 B4138 ; configure sensor 0 as thermistor on pin temp0
    M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
    M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
    M140 H0 ; map heated bed to heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C

    M308 S1 P"124.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin 121.temp0
    M950 H1 C"124.out0" T1 ; create nozzle heater output on 121.out0 and map it to ;sensor 1
    M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
    M143 H1 S280 ; set temperature limit for heater 1 to 280C

    ;routine for PID calibration

    ;M308 S1 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin 121.temp0
    ;M950 H1 C"out0" T1 ; create nozzle heater output on 121.out0 and map it to sen
    ;M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
    ;M143 H1 S280

    ;end routine

    ; Fans
    ;M950 F0 C"laser" ; create fan 0 on pin 121.out1 and set its frequency
    ;M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off

    M950 F0 c"124.out2" Q250
    M106 P0 S0 h-1

    M950 F1 C"vfd" Q500 ; create fan 1 on pin vfd and set its frequency
    M106 P1 S1 H-1

    m950 F2 C"124.OUT1" Q250
    M106 P2 T35 S255 H1 ; set fan 1 value. Thermostatic control is turned off

    ; Tools
    M563 P0 D0 H1 F0 ; define tool 0
    G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
    G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

    M572 D0 S0.035 ;SET PRESSURE ADVANCE

    M955 P124.0 I02 ; ;ACCELEROMETER

    M308 S2 P"124.temp1" Y"thermistor" A"Chamber Temperature" T100000 B4092 ;CHAMBER TEMP

    M593 P"zvd" F45 ;CONFIGURE INPUT SHAPING

    M591 D0 P1 C"io1.in" s1 ;CONFIGURE FILAMENT SWITCH

    ; Custom settings are not defined

    ; Miscellaneous
    M501 ; load saved parameters from non-volatile memory
    M911 S22 R22.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
    T0 ; select first tool

    8/4/2024, 11:25:47 AM: m122 b124: Diagnostics for board 124:
    Duet FLY36RRF firmware version 3.5.2 (2024-06-13 00:56:43)
    Bootloader ID:
    All averaging filters OK
    Never used RAM 218224, free system stack 436 words
    Tasks: Move(3,nWait 7,0.0%,132) HEAT(2,nWait 6,0.2%,116) CanAsync(5,nWait 4,0.0%,64) CanRecv(3,nWait 1,0.0%,356) CanClock(5,nWait 1,0.0%,334) ACCEL(3,nWait 6,0.0%,52) TMC(2,delaying,2.3%,52) MAIN(1,running,95.7%,434) IDLE(0,ready,0.0%,26) USBD(2,blocked,0.0%,150) AIN(2,delaying,1.8%,248), total 100.0%
    Owned mutexes:
    Last reset 00:39:32 ago, cause: power up or brownout
    Last software reset data not available
    Driver 0: pos 0, 690.0 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 55332, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
    Peak sync jitter -11/18, peak Rx sync delay 339, resyncs 0/0, no timer interrupt scheduled
    VIN voltage: min 23.7, current 23.7, max 23.8
    MCU temperature: min 29.0C, current 39.3C, max 39.8C
    Last sensors broadcast 0x00000006 found 2 11 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 72644, send timeouts 0, received 23597, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
    Accelerometer: LIS3DH, status: 00
    8/4/2024, 11:25:52 AM: m122 b120: Diagnostics for board 120:
    Duet SZP firmware version 3.5.2 (2024-06-10 13:23:26)
    Bootloader ID: SAMC21 bootloader version 2.10 (2023-11-16)
    All averaging filters OK
    Never used RAM 14000, free system stack 110 words
    Tasks: HEAT(2,nWait 6,0.1%,132) CanAsync(5,nWait 4,0.0%,54) CanRecv(3,nWait 1,0.0%,70) CanClock(5,nWait 1,0.0%,58) ACCEL(3,nWait 6,0.0%,52) MAIN(1,running,71.8%,420) IDLE(0,ready,0.0%,26) AIN(2,nWait 2,28.0%,72), total 100.0%
    Owned mutexes:
    Last reset 00:39:36 ago, cause: power up
    Last software reset data not available
    Peak sync jitter -3/8, peak Rx sync delay 214, resyncs 0/0, no timer interrupt scheduled
    VIN voltage: min 5.0, current 5.0, max 5.0
    MCU temperature: min 23.2C, current 27.6C, max 27.8C
    Last sensors broadcast 0x00000400 found 1 157 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 4737, send timeouts 0, received 7670, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
    Accelerometer: LIS2DW, status: 00
    Inductive sensor: raw value 36950956, frequency 3.44MHz, current setting 15, ok
    I2C bus errors 0, naks 0, contentions 0, other errors 0
    8/4/2024, 11:25:58 AM: m122: === Diagnostics ===
    RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode)
    Board ID: 6KSY8-12401-8D3J0-4018D-MYS0Z-ZKUV9
    Used output buffers: 3 of 40 (34 max)
    === RTOS ===
    Static ram: 103368
    Dynamic ram: 123036 of which 24 recycled
    Never used RAM 14988, free system stack 202 words
    Tasks: NETWORK(2,nWait 7,14.1%,240) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,331) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,796) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,1.4%,101) MAIN(1,running,83.6%,665) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.8%,259), total 100.0%
    Owned mutexes:
    === Platform ===
    Last reset 00:39:42 ago, cause: power up
    Last software reset at 2024-08-03 17:30, reason: User, Gcodes spinning, available RAM 11452, slot 1
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    MCU revision 0, ADC conversions started 2382981, completed 2382981, timed out 0, errs 0
    MCU temperature: min 35.0, current 35.6, max 36.1
    Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
    Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
    Events: 0 queued, 0 completed
    Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 53734, writes 0, timeouts 0, DMA errors 0, CC errors 0
    Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 53734, writes 0, timeouts 0, DMA errors 0, CC errors 0
    Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 53735, writes 0, timeouts 0, DMA errors 0, CC errors 0
    Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 53735, writes 0, timeouts 0, DMA errors 0, CC errors 0
    Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 53734, writes 0, timeouts 0, DMA errors 0, CC errors 0
    Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 53735, writes 0, timeouts 0, DMA errors 0, CC errors 0
    Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 53735, writes 0, timeouts 0, DMA errors 0, CC errors 0
    Date/time: 2024-08-04 11:25:57
    Cache data hit count 4294967295
    Slowest loop: 26.18ms; fastest: 0.16ms
    === Storage ===
    Free file entries: 20
    SD card 0 detected, interface speed: 22.5MBytes/sec
    SD card longest read time 3.6ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
    no step interrupt scheduled
    Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
    === DDARing 0 ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === DDARing 1 ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Movement locks held by null, null
    HTTP is idle 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
    File2 is idle in state(s) 0
    Queue2 is idle in state(s) 0
    Q0 segments left 0, axes/extruders owned 0x0000803
    Code queue 0 is empty
    Q1 segments left 0, axes/extruders owned 0x0000000
    Code queue 1 is empty
    === Filament sensors ===
    check 0 clear 11605462
    Extruder 0 sensor: ok
    === CAN ===
    Messages queued 5336, received 16598, lost 0, errs 0, boc 0
    Longest wait 7ms for reply type 6024, peak Tx sync delay 6, free buffers 26 (min 25), ts 2955/2955/0
    Tx timeouts 0,0,0,0,0,0
    === Network ===
    Slowest loop: 200.31ms; fastest: 0.01ms
    Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    HTTP sessions: 1 of 8
    === WiFi ===
    Interface state: active
    Module is connected to access point
    Failed messages: pending 0, notrdy 4, noresp 1
    Firmware version 2.1.0
    MAC address bc:ff:4d:e6:b1:78
    Module reset reason: Hardware watchdog, Vcc 3.39, flash size 2097152, free heap 43044
    WiFi IP address 192.168.1.111
    Signal strength -59dBm, channel 4, mode 802.11n, reconnections 0
    Clock register 00002002
    Socket states: 0 0 0 0 0 0 0 0

    undefined 1 Reply Last reply 4 Aug 2024, 16:03 Reply Quote 0
    • undefined
      gloomyandy @Invader_Zoom
      last edited by 4 Aug 2024, 16:03

      @Invader_Zoom Do you have any deployprobe files in your sys directory? If so what is in them?

      undefined 1 Reply Last reply 4 Aug 2024, 17:13 Reply Quote 0
      • undefined
        Invader_Zoom @gloomyandy
        last edited by 4 Aug 2024, 17:13

        @gloomyandy

        Yes, I am using deployprobe.g and retractprobe.g subroutines containing a single M280 command each.

        M280 P0 s10 extend

        M280 P0 S90 retract

        undefined 1 Reply Last reply 4 Aug 2024, 18:34 Reply Quote 0
        • undefined
          gloomyandy @Invader_Zoom
          last edited by 4 Aug 2024, 18:34

          @Invader_Zoom Try renaming those to deployprobe0.g and retractprobe0.g at the moment I think it may be running your current files for both probes.

          undefined undefined 2 Replies Last reply 4 Aug 2024, 20:56 Reply Quote 3
          • undefined
            Invader_Zoom @gloomyandy
            last edited by 4 Aug 2024, 20:56

            @gloomyandy Renaming the deploy and retract subroutines solved my issue. Thank you for your help.

            1 Reply Last reply Reply Quote 1
            • undefined Phaedrux marked this topic as a question 5 Aug 2024, 04:06
            • undefined Phaedrux has marked this topic as solved 5 Aug 2024, 04:06
            • undefined
              tbahre @gloomyandy
              last edited by 5 Jan 2025, 21:07

              @gloomyandy after spending all day fighting my SZP I finally stumbled upon your answer and it saved my brain from having a total meltdown. This really needs to be put into the official documentation asap. I really like my duet stuff but it's things like this that drive me nuts, the documentation is missing critical things like this. Thank you thank you!

              undefined 1 Reply Last reply 5 Jan 2025, 21:24 Reply Quote 0
              • undefined
                Phaedrux Moderator @tbahre
                last edited by 5 Jan 2025, 21:24

                @tbahre said in BL Probe deploys when Scanning Z probe cycles run:

                @gloomyandy after spending all day fighting my SZP I finally stumbled upon your answer and it saved my brain from having a total meltdown. This really needs to be put into the official documentation asap. I really like my duet stuff but it's things like this that drive me nuts, the documentation is missing critical things like this. Thank you thank you!

                @droftarts Paging Doctor Tarts

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 3
                3 out of 7
                • First post
                  3/7
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA