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

    Scanning Z probe support in RRF 3.5

    Scheduled Pinned Locked Moved
    Beta Firmware
    23
    128
    10.1k
    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.
    • flyschaundefined
      flyscha @dc42
      last edited by

      @dc42 Thank you for the update! I deleted the Duet3Firmware_SZP.bin file from my SBC's SD card, and put the new file in its place.

      Regarding the other files from your link, (SZP.map, TOOL1RR.bin, and TOOL1RR.map), do I need to upload/replace those somewhere as well?

      Just checking because the SZP Documentation page just mentions the Duet3Firmware_SZP.bin file being needed.

      With only the SZP.bin file replaced, I'm still getting the same errors of:

      -Error: sensor error during calibration
      -Error: Bad reading from scanning probe - try recalibrating the probe

      Here are the diagnostics as well:

      m122 b69
      Diagnostics for board 69:
      Duet SZP firmware version 3.5.0-rc.2 (2023-12-14 08:58:41)
      Bootloader ID: SAMC21 bootloader version 2.10 (2023-11-16)
      All averaging filters OK
      Never used RAM 14496, 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.2%,92), total 100.0%
      Last reset 00:06:13 ago, cause: software
      Last software reset data not available
      Peak sync jitter 1/5, peak Rx sync delay 207, resyncs 0/0, no timer interrupt scheduled
      VIN voltage: min 4.9, current 5.0, max 5.0
      MCU temperature: min 24.9C, current 25.2C, max 25.3C
      Last sensors broadcast 0x00000000 found 0 76 ticks ago, 0 ordering errs, loop time 0
      CAN messages queued 1972, send timeouts 0, received 3785, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
      Accelerometer: LIS2DW, status: 00
      Inductive sensor: raw value 42133425, frequency 3.92MHz, current setting 13, ok
      I2C bus errors 1344, naks 3, contentions 0, other errors 0

      Thanks!

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @flyscha
        last edited by

        @flyscha that shows your board hasn't updated. the build date is still the RC2 release, not the latest one from dc42

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        flyschaundefined 1 Reply Last reply Reply Quote 1
        • flyschaundefined
          flyscha @jay_s_uk
          last edited by

          @jay_s_uk I'm seeing what you're seeing as well, where it's still showing the older version.

          Given that, the beginning of my last post seems to be the culprit:

          I deleted the Duet3Firmware_SZP.bin file from my SBC's SD card, and put the new file in its place.

          Regarding the other files from your link, (SZP.map, TOOL1RR.bin, and TOOL1RR.map), do I need to upload/replace those somewhere as well?

          Just checking because the SZP Documentation page just mentions the Duet3Firmware_SZP.bin file being needed.

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @flyscha
            last edited by

            @flyscha you don't need those. the board i have here flashed ok

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            flyschaundefined 1 Reply Last reply Reply Quote 0
            • flyschaundefined
              flyscha @jay_s_uk
              last edited by flyscha

              @jay_s_uk Ok thanks! Are you using an SBC?

              jay_s_ukundefined 2 Replies Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @flyscha
                last edited by

                @flyscha no, standalone

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @flyscha
                  last edited by

                  @flyscha if you're using DWC to upload it should ask you to update. if you're pulling the SD card and loading the file you'll need to send M997 B69

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  flyschaundefined 1 Reply Last reply Reply Quote 1
                  • flyschaundefined
                    flyscha @jay_s_uk
                    last edited by

                    @jay_s_uk Thank you! I for sure ran the M997 B69 after replacing the .bin file on the SD card last night, but maybe something got mixed up when moving bin files around.

                    I'll try it all again tonight. Much appreciated!

                    flyschaundefined 1 Reply Last reply Reply Quote 1
                    • flyschaundefined
                      flyscha @flyscha
                      last edited by

                      @jay_s_uk I tried over and over and over and somehow FINALLY the firmware updated! I must have tried 5 or 6 times, and it just so happened to stick. I won't speak too loudly or else it may scare it back to the previous version.

                      @dc42 The new firmware was absolutely the fix for me! Now when I run the M122 diagnostics, I get 0 I2C bus errors. Every now and then there are a few naks (always 0 or 3), but that's about it.

                      When sending the G29 command, I now get scanning probe coefficients, and the entire bed scans without any stops, errors, or hiccups.

                      Thanks for everyone's help!

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

                        @flyscha I'm glad it's working for you.

                        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

                        1 Reply Last reply Reply Quote 0
                        • becky9undefined
                          becky9
                          last edited by

                          Where can I get the scanning probe in the UK at the moment? Looked on E3D & Ooznest can't see it x

                          T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
                          • tkamskerundefined
                            tkamsker
                            last edited by

                            @dc42 said in Scanning Z probe support in RRF 3.5:

                            https://www.youtube.com/watch?v=969s3J8EEyM

                            Hi i might being late to that thread but i have an (several) duet 2 boards and i would love to upgrade my E3D tool changer to that Z-Probe so question how is that possible ? i see all infos refer to Duet 3 board ,. i would love to not totally rework my printers thx thomas

                            jay_s_ukundefined dc42undefined 2 Replies Last reply Reply Quote 0
                            • jay_s_ukundefined
                              jay_s_uk @tkamsker
                              last edited by

                              @tkamsker it doesn't support duet 2 boards as it requires CAN-FD (which the duet 2 doesn't support)

                              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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

                                @tkamsker also we have run out of flash memory space in Duet 2. After 3.5 I expect to move Duet 2 and Maestro firmware to "bug fixes only" maintenance status because it doesn't have enough flash or RAM space for significant new features.

                                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

                                1 Reply Last reply Reply Quote 3
                                • T3P3Tonyundefined
                                  T3P3Tony administrators @becky9
                                  last edited by

                                  @becky9 we are working on it, in the meantime if you drop an email to sales@duet3d.com we should be able to help.

                                  www.duet3d.com

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA