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

    Scanning Z probe G31: invalid Z probe index

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    4
    9
    381
    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.
    • charliedrumsundefined
      charliedrums
      last edited by

      Ok, so I have the scanning z probe connected M122 B120 command works and I get communication with the board.

      M122 b120
      Diagnostics for board 120:
      Duet SZP firmware version 3.5.0-rc.1+ (2023-11-20 12:50:20)
      Bootloader ID: SAMC21 bootloader version 2.10 (2023-11-16)
      All averaging filters OK
      Never used RAM 14416, free system stack 136 words
      Tasks: HEAT(2,nWait,0.1%,131) CanAsync(5,nWait,0.0%,55) CanRecv(3,nWait,0.0%,79) CanClock(5,nWait,0.0%,67) ACCEL(3,nWait,0.0%,53) MAIN(1,running,99.7%,434) IDLE(0,ready,0.0%,27) AIN(2,nWait,0.1%,92), total 100.0%
      Last reset 00:04:53 ago, cause: software
      Last software reset data not available
      Peak sync jitter 1/5, peak Rx sync delay 204, resyncs 0/0, no timer interrupt scheduled
      VIN voltage: min 4.9, current 4.9, max 4.9
      MCU temperature: min 23.9C, current 24.2C, max 24.4C
      Last sensors broadcast 0x00000400 found 1 135 ticks ago, 0 ordering errs, loop time 0
      CAN messages queued 2324, send timeouts 0, received 3744, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
      Accelerometer: LIS2DW, status: 00
      Inductive sensor: raw value 42434148, frequency 3.95MHz, current setting 13, amplitude error
      I2C bus errors 34, naks 3, contentions 0, other errors 0
      

      I have configured my config.g probes as follows.

      ; Z-Probe
      M558 K0 P5 C"!io7.in" H3 F900:120 T15000; 
      G31 K0 P500 X-31.27 Y-46.64 Z1.44;
      M557 X29:609 Y40:603 P21:21;
      
      ; Scanning Z probe
      M558 K1 P11 C"120.i2c.ldc1612" F24000 T24000    ; 
      M308 A"SZP coil" S10 Y"thermistor" P"120.temp0" ; 
      G31 K1 Z2 Y-17 ;
      M557 X29:609 Y40:603 P21:21; 
      

      But all I get when I start the duet is:

      1/31/2024, 9:29:52 PM 	Error in start-up file config.g line 62: G31: invalid Z probe index
      1/31/2024, 9:29:52 PM 	Error: G31: invalid Z probe index
      

      I’m running RRF 3.5rc3 A toolboard 1LC and the Z scanning probe is connected to the tool distribution board. Is the scanning probe supported on a tool distribution board? Any help would be greatly appreciated.

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.3 (2024-01-24 17:58:49) running on Duet 3 MB6HC v1.01 (SBC mode)
      Board ID: 08DJM-956BA-NA3TN-6JTD0-3SJ6S-1V82V
      Used output buffers: 1 of 40 (28 max)
      Error in macro line 62 while starting up: G31: invalid Z probe index
      === RTOS ===
      Static ram: 155184
      Dynamic ram: 87480 of which 5392 recycled
      Never used RAM 95080, free system stack 202 words
      Tasks: SBC(2,ready,0.8%,440) HEAT(3,nWait 6,0.0%,323) Move(4,nWait 6,0.0%,336) CanReceiv(6,nWait 1,0.0%,795) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,8.2%,56) MAIN(2,running,90.8%,103) IDLE(0,ready,0.2%,30), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:15:39 ago, cause: software
      Last software reset at 2024-02-01 02:29, reason: User, Gcodes spinning, available RAM 95080, slot 1
      Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      MCU temperature: min 37.6, current 37.8, max 38.5
      Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.1, current 12.1, max 12.1, under voltage events: 0
      Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/40/0, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min n/a, mspos 840, reads 13641, writes 14 timeouts 0
      Driver 1: standstill, SG min n/a, mspos 200, reads 13641, writes 14 timeouts 0
      Driver 2: standstill, SG min n/a, mspos 952, reads 13641, writes 14 timeouts 0
      Driver 3: standstill, SG min n/a, mspos 88, reads 13641, writes 14 timeouts 0
      Driver 4: standstill, SG min n/a, mspos 88, reads 13641, writes 14 timeouts 0
      Driver 5: standstill, SG min n/a, mspos 952, reads 13642, writes 14 timeouts 0
      Date/time: 2024-02-01 02:45:19
      Slowest loop: 19.77ms; fastest: 0.06ms
      === Storage ===
      Free file entries: 20
      SD card 0 not detected, interface speed: 37.5MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      === GCodes ===
      Movement locks held by null, null
      HTTP* is doing "M122" 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 0x0000000
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === Filament sensors ===
      check 0 clear 0
      Extruder 0 sensor: no data received
      === CAN ===
      Messages queued 8445, received 26647, lost 0, errs 1, boc 0
      Longest wait 3ms for reply type 6024, peak Tx sync delay 228, free buffers 50 (min 49), ts 4700/4699/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      Transfer state: 5, failed transfers: 0, checksum errors: 0
      RX/TX seq numbers: 36111/36111
      SPI underruns 0, overruns 0
      State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x255cc
      Buffer RX/TX: 0/0-0, open files: 0
      === Duet Control Server ===
      Duet Control Server version 3.5.0-rc.3 (2024-01-26 12:34:19)
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
      Full transfers per second: 38.67, max time between full transfers: 937.3ms, max pin wait times: 932.0ms/14.0ms
      Codes per second: 0.06
      Maximum length of RX/TX data transfers: 4365/704
      
      M122 B121
      Diagnostics for board 121:
      Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.3 (2024-01-24 17:55:14)
      Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
      All averaging filters OK
      Never used RAM 3368, free system stack 136 words
      Tasks: Move(3,nWait 7,0.0%,135) HEAT(2,nWait 6,0.2%,129) CanAsync(5,nWait 4,0.0%,55) CanRecv(3,nWait 1,0.0%,71) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,delaying,3.4%,53) MAIN(1,running,91.6%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.7%,112), total 100.0%
      Owned mutexes:
      Last reset 00:16:33 ago, cause: software
      Last software reset data not available
      Driver 0: pos 0, 405.0 steps/mm, standstill, SG min 2, read errors 0, write errors 1, ifcnt 120, reads 37744, writes 12, 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 1/5, peak Rx sync delay 213, resyncs 0/0, no timer interrupt scheduled
      VIN voltage: min 24.5, current 24.5, max 24.5
      MCU temperature: min 37.5C, current 37.6C, max 37.9C
      Last sensors broadcast 0x00000002 found 1 45 ticks ago, 0 ordering errs, loop time 0
      CAN messages queued 20260, send timeouts 0, received 12848, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
      Accelerometer: LIS3DH, status: 00
      I2C bus errors 0, naks 3, contentions 0, other errors 0
      === Filament sensors ===
      Interrupt 5726621 to 0us, poll 4 to 665us
      Driver 0: no data received
      
      dc42undefined gloomyandyundefined 2 Replies Last reply Reply Quote 0
      • oliofundefined
        oliof
        last edited by

        share your full config g please

        <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

        charliedrumsundefined 1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators @charliedrums
          last edited by

          @charliedrums without seeing your full config.g file we can only guess at the cause. My guess is that you need to add a delay command such as G1 S4 near the start of config to allow time for the SZP board to start up before you address it in the M558 K1 command.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          charliedrumsundefined 1 Reply Last reply Reply Quote 0
          • gloomyandyundefined
            gloomyandy @charliedrums
            last edited by

            @charliedrums said in Scanning Z probe G31: invalid Z probe index:

            uet SZP firmware version 3.5.0-rc.1+ (2023-11-20 12:50:20)

            Your SZP does not seem to be running 3.5.0-rc.3. Probably best to make sure all of the boards are using the same version.

            charliedrumsundefined 1 Reply Last reply Reply Quote 2
            • charliedrumsundefined
              charliedrums
              last edited by

              @charliedrums said in Scanning Z probe G31: invalid Z probe index:

              ; Z-Probe
              Here is the complete config file:

              ; Configuration file for Duet 3 
              ; executed by the firmware on start-up
              ;
              ; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Feb 16 2022 21:57:55 GMT-0500 (Eastern Standard Time)
              
              ; General preferences
              M575 P1 S1 B57600                                         ; enable support for PanelDue
              G90                                                       ; send absolute coordinates...
              M83                                                       ; ...but relative extruder moves
              M550 P"duet3"                                             ; set printer name
              M669 K1                                                   ; select CoreXY mode
              M929 P"eventlog.txt" S1                                   ; start logging warnings to file eventlog.txt
              
              ; Wait a moment for the CAN expansion boards to start
              G4 S2
              
              ; Network
              ;M552 P0.0.0.0 S1                                          ; enable network and acquire dynamic address via DHCP
              ;M586 P0 S1                                                ; enable HTTP
              ;M586 P1 S0                                                ; disable FTP
              ;M586 P2 S0                                                ; disable Telnet
              
              ; Drives
              M569 P0.0 S1                                              ; physical drive 0.0 goes forwards (X-Y)
              M569 P0.1 S1                                              ; physical drive 0.1 goes forwards (X-Y)
              M569 P0.2 S0                                              ; physical drive 0.2 goes forwards
              M569 P0.3 S1                                              ; physical drive 0.3 goes forwards
              M569 P0.4 S1                                              ; physical drive 0.4 goes forwards
              M569 P0.5 S0                                              ; physical drive 0.5 goes forwards
              M569 P121.0 S0                                            ; physical drive 121.0 goes forwards
              M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 E121.0                    ; set drive mapping
              M671 X35:790:100:780 Y-105:-105:665:665 S10	           	  ; set Z belt positions, max error 5mm
              M350 X16 Y16 Z16 E16 I1                                   ; configure microstepping with interpolation
              M92 X80.00 Y80.00 Z800.00 E405.00                         ; set steps per mm
              M566 X420.00 Y420.00 Z60.00 E960.00                       ; set maximum instantaneous speed changes (Jerk)(mm/min)
              M203 X24000.00 Y24000.00 Z1200 E7200               ; 120 set maximum speeds (mm/min)  450, 450, 420, 167
              M201 X1500.00 Y1500.00 Z300.00 E5000.00                   ; set accelerations (mm/s^2)
              ; M204 P1500 T2000                                         ; Set printing acceleration and travel accelerations
              M906 X1000 Y1000 Z1000 E800 I30                           ; set motor currents (mA) and motor idle factor in per cent
              M84 S30                                                   ; Set idle timeout
              
              ; Axis Limits
              M208 X0 Y0 Z0 S1                                          ; set axis minima
              M208 X670 Y650 Z645 S0                                    ; set axis maxima
              
              ; Endstops
              M574 X1 S1 P"!^io3.in"                                    ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !^io3.in
              M574 Y2 S1 P"!^io1.in"                                    ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io1.in
              M574 Z1 S2                                                ; configure Z-probe endstop for low end on Z
              
              ; Z-Probe
              M558 K0 P5 C"!io7.in" H3 F900:120 T15000; 
              G31 K0 P500 X-31.27 Y-46.64 Z1.44;
              M557 X29:609 Y40:603 P21:21;
               
              ; Scanning Z probe
              M558 K1 P11 C"120.i2c.ldc1612" F24000 T24000    ; 
              M308 A"SZP coil" S10 Y"thermistor" P"120.temp0" ; 
              G31 K1 Z2 Y-17 ;
              M557 X29:609 Y40:603 P21:21; 
              
              ; Filament Sensor
              ; M591 D0 P3 C"121.io1.in" S1 L24.84 R35:130 E5           ; Duet3D Rotating Magnet Filament Monitor connected to Toolboard 1LC io1
              ; M591 D0 P1 C"121.io2.in" S1                             ; Dyze Design SENTINEL Filament Detector connected to Toolboard 1LC io2
              M591 D0 P7 C"121.io2.in" S1 L1.246 R50:200 E40             ; Dyze Design SENTINEL Filament Detector connected to Toolboard 1LC io2
              
              ; Heaters
              M308 S0 P"temp0" Y"thermistor" T100000 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 B0 R0.391 C260.7 D2.75 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"121.temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin 121.temp0
              M950 H1 C"121.out0" T1                                    ; create nozzle heater output on 121.out0 and map it to sensor 1
              M307 H1 R4.349 K0.448:0.346 D1.66 E1.35 S1.00 B0 V24.1    ;M307 H1 B0 R1.891 C265.1 D5.94 S1.00 V24.2; disable bang-bang mode for heater  and set PWM limit
              M143 H1 S280                                              ; set temperature limit for heater 1 to 280C
              
              ; Fans
              M950 F0 C"121.out1" Q500                                  ; 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 F1 C"121.out2" Q500                                  ; create fan 1 on pin 121.out2 and set its frequency
              M106 P1 S1 H1 T45                                         ; set fan 1 value. Thermostatic control is turned on
              
              ; Accelerometer
              M955 P121.0 I54 ; specify orientation of accelerometer on Toolboard 1LC with CAN address 121
              
              ; Low power automatic pause and save
              M911 S23.2 R23.25 P"M913 X0 Y0 Z0 E0 M104 S0 M140 S0 M107"; G91 M83 G1 Z1"    ;
              
              ; Tools
              M563 P0 D0 H1 F0:1                                        ; 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
              
              ; Firmware Retraction
              ;M207 S0.6 F2400 Z0.4                                     
              
              ; Custom settings are not defined
              M572 D0 S0.018						                      ; pressure advance
              M593 P"zvddd" F24.3				                              ; input shaping 
              
              1 Reply Last reply Reply Quote 0
              • charliedrumsundefined
                charliedrums @gloomyandy
                last edited by

                @gloomyandy I run in SBC and I did try to do an update but it did not update the Scanning probe board. Should I run it again?

                1 Reply Last reply Reply Quote 0
                • charliedrumsundefined
                  charliedrums @oliof
                  last edited by

                  @oliof I triedthe G1 S4 after the G4 S2 but still get the G31: invalid Z probe index

                  ; Wait a moment for the CAN expansion boards to start
                  G4 S2
                  G1 S4
                  
                  1 Reply Last reply Reply Quote 0
                  • charliedrumsundefined
                    charliedrums
                    last edited by

                    A bit more info on my setup.
                    I have the 1LC board connected to Tool0 connection on the tool distribution board and the scanning z probe on Tool1 I left the BYPASS jumpers on the on Tool 1 and I also soldered the termination resistor jumper on the back of the scanning Z Probe board.

                    Screenshot 2024-02-01 141737.png

                    1 Reply Last reply Reply Quote 0
                    • charliedrumsundefined
                      charliedrums @dc42
                      last edited by charliedrums

                      @gloomyandy said in Scanning Z probe G31: invalid Z probe index:

                      @charliedrums said in Scanning Z probe G31: invalid Z probe index:

                      uet SZP firmware version 3.5.0-rc.1+ (2023-11-20 12:50:20)

                      Your SZP does not seem to be running 3.5.0-rc.3. Probably best to make sure all of the boards are using the same version.

                      Totally brain farted, this was the issue. I was trying to update the SZP board trough putty with sudo apt update but it kept saying everything was updated. Fetched the rc3 update bin file for the SZP from the github directory and uploaded it trough DWC and installed it from there. That seemed to be my problem. I don't get the G31: invalid Z probe index at start up anymore. Thanks everyone for the help.

                      1 Reply Last reply Reply Quote 2
                      • dc42undefined dc42 marked this topic as a question
                      • dc42undefined dc42 has marked this topic as solved
                      • First post
                        Last post
                      Unless otherwise noted, all forum content is licensed under CC-BY-SA