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

Weird behaviour after first print

Scheduled Pinned Locked Moved
Beta Firmware
8
29
1.8k
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
    MartinNYHC
    last edited by MartinNYHC 15 Aug 2021, 12:56

    Problem is still there 🤕

    There is a new additional error message after the upgrade.

    **Error: G32 has thrown an exception: [NullReferenceException] Object reference not set to an instance of an object.**
    Error: Probe already triggered at start of probing move
    
    1 Reply Last reply Reply Quote 0
    • undefined
      MartinNYHC
      last edited by 15 Aug 2021, 17:49

      And with G29 I now get

      Screenshot 2021-08-15 at 19.48.23.png

      undefined 1 Reply Last reply 16 Aug 2021, 09:23 Reply Quote 0
      • undefined
        chrishamm administrators @MartinNYHC
        last edited by 16 Aug 2021, 09:23

        @martinnyhc There must be an exception or cancelled code somewhere in your bed.g which is why you get that exception. I've got a fix ready that will be included in 3.4-b3. Also you seem to call G29 without S parameter in mesh.g, which will invoke mesh.g over and over again until you get a stack overflow.

        Duet software engineer

        1 Reply Last reply Reply Quote 0
        • undefined
          MartinNYHC
          last edited by 16 Aug 2021, 11:09

          Yep, already fixed that. I need to do some further testing regarding the probe. In the meantime if did a fresh SBC install.

          1 Reply Last reply Reply Quote 0
          • undefined
            MartinNYHC
            last edited by 16 Aug 2021, 15:20

            OK, spent the day with doing a clean SBC install (RRF 3.3.0) and rewriting all config files and macros. The main issue I have still persists. Gantry and bed leveling works like charm if it is the first print. As soon as a print finished or where cancelled and I start a new print it fails.

            Fails means for example: The first thing of course is homing. Second thing is gantry leveling.

            ; bed.g
            ; called to perform automatic bed compensation via G32
            
            if !move.axes[0].homed && !move.axes[1].homed && !move.axes[2].homed
            	G28 ; home
            
            M558 K0 H10 F400												; set trigger height
            
            M561 															; clear any bed transform
            
            M98 P"0:/macros/sys/undock_klicky_probe.g"						; undock clicky probe
            
            while iterations <=1											; first pass
            	G30 P0 X20 Y25 Z-99999 F9000 								; probe Z left front
            	G30 P1 X20 Y320 Z-99999 F9000      							; probe Z left rear
            	G30 P2 X330 Y320 Z-99999 F9000 							    ; probe Z right rear
            	G30 P3 X330 Y25 Z-99999 S4 F9000 							; probe Z right front
            	G1 H2 Z12 F2600 											; raise head
            	M400 														; finish move, clear buffer
            	M558 K0 H2.5 F200											; trigger height to 2.5mm after first run
            
            while move.calibration.initial.deviation >= 0.003          		; Perform additional leveling if previous deviation was over 0.03mm.
            	G30 P0 X20 Y25 Z-99999 F9000 								; probe Z left front
            	G30 P1 X20 Y320 Z-99999 F9000      							; probe Z left rear
            	G30 P2 X330 Y320 Z-99999 F9000 							    ; probe Z right rear
            	G30 P3 X330 Y25 Z-99999 S4 F9000 							; probe Z right front
            	G1 H2 Z12 F2600 											; raise head
            	M400 														; finish move, clear buffer
            
            echo "Gantry deviation of " ^ move.calibration.initial.deviation ^ "mm obtained."
            
            G1 Z12                                         					; Raise nozzle
            
            M98 P"0:/macros/sys/dock_klicky_probe.g"						; dock clicky probe
            	  
            G28 															; Homing again for accurate Z offset
            

            It probes the four points for the first time, changes the probing height and probes for the second time. Suddenly it is just going to the probe points but don't lower Z to probe the bed.

            Here's an archive of my complete config. I've spent so many days with this problem now and did everything which came to my mind, I'm definitely stuck and don't now what to do.

            Help please! 🤕 Thanks in advance!

            Complete Config

            1 Reply Last reply Reply Quote 0
            • undefined
              Phaedrux Moderator
              last edited by 16 Aug 2021, 16:06

              Are there example configs from other voron users that use this probe?

              Have you tested in standalone mode as a control?

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • undefined
                MartinNYHC
                last edited by 16 Aug 2021, 16:09

                There are many many other users and I took over the config from them. And it already worked for multiple weeks.

                Nope, not tested standalone. But as said I just did acomplete fresh SBC install.

                undefined 1 Reply Last reply 16 Aug 2021, 16:46 Reply Quote 0
                • undefined
                  Phaedrux Moderator
                  last edited by 16 Aug 2021, 16:36

                  Well I'd say either test your current config files in standalone mode to eliminate the SBC for testing, or wait for chrishamms updated build.
                  Right now we're mixing 3 confounding factors, unproven macros, SBC mode, and beta firmware. When in doubt, try and roll it back to the most basic configuration and when it's working, start adding new things one at a time.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    jay_s_uk @MartinNYHC
                    last edited by 16 Aug 2021, 16:46

                    @martinnyhc try

                    ; bed.g
                    ; called to perform automatic bed compensation via G32
                     
                    if !move.axes[0].homed && !move.axes[1].homed && !move.axes[2].homed
                    	G28 ; home
                     
                    M558 K0 H10 F400												; set trigger height
                     
                    M561 															; clear any bed transform
                     
                    M98 P"0:/macros/sys/undock_klicky_probe.g"						; undock clicky probe
                     
                    G30 P0 X20 Y25 Z-99999 F9000 								; probe Z left front
                    G30 P1 X20 Y320 Z-99999 F9000      							; probe Z left rear
                    G30 P2 X330 Y320 Z-99999 F9000 							    ; probe Z right rear
                    G30 P3 X330 Y25 Z-99999 S4 F9000 							; probe Z right front
                    G1 H2 Z12 F2600 											; raise head
                    M400 														; finish move, clear buffer
                    M558 K0 H2.5 F200											; trigger height to 2.5mm after first run
                     
                    while move.calibration.initial.deviation >= 0.003          		; Perform additional leveling if previous deviation was over 0.03mm.
                       if iterations = 5
                          abort "Too many auto tramming attempts"
                       G30 P0 X20 Y25 Z-99999 F9000 								; probe Z left front
                       G30 P1 X20 Y320 Z-99999 F9000      							; probe Z left rear
                       G30 P2 X330 Y320 Z-99999 F9000 							    ; probe Z right rear
                       G30 P3 X330 Y25 Z-99999 S4 F9000 							; probe Z right front
                       G1 H2 Z12 F2600 											; raise head
                       M400 														; finish move, clear buffer
                       echo "BTC: " ^ iterations + 2 ^ " - Difference was " ^ move.calibration.initial.deviation ^ "mm"
                       continue
                     
                    G1 Z12                                         					; Raise nozzle
                     
                    M98 P"0:/macros/sys/dock_klicky_probe.g"						; dock clicky probe
                    	  
                    G28 								
                    

                    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
                    • undefined
                      medicusdkfz
                      last edited by 10 Sept 2021, 11:49

                      Did you solve your problem? I'm struggling with QGL and mesh with the klicky probe... My problem is, that I use the autoz calculation macro at first and then I try to perform a QGL... After the homing and autoZ macro, the Z0 is at the surface of the bed plate - as expected. But then my QGL fails...

                      undefined 1 Reply Last reply 10 Sept 2021, 12:09 Reply Quote 0
                      • undefined
                        MartinNYHC @medicusdkfz
                        last edited by 10 Sept 2021, 12:09

                        @medicusdkfz For me it was a loose connection on the klicky probe which only occured randomly.

                        undefined 1 Reply Last reply 10 Sept 2021, 12:12 Reply Quote 0
                        • undefined
                          medicusdkfz @MartinNYHC
                          last edited by medicusdkfz 9 Oct 2021, 12:15 10 Sept 2021, 12:12

                          @martinnyhc Please would you share your RRF3-configuration with me? You'll find my mail adress in my profile...

                          Thank you in advance...

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            medicusdkfz
                            last edited by 10 Sept 2021, 12:14

                            How is your process for creating a mesh from scratch? Do you also use a seperate z-microswitch for calculate the difference between the nozzle and the switch point of the klicky probe?

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              sinned6915
                              last edited by sinned6915 19 Sept 2021, 04:11

                              You have to call the probe deploy from within your homez and then again in your beg.g or other macros that need the probe. Conditonal gcode makes this an easy check and remedy.

                              The error is because the NC probe state is 1000 when the probe is not connected or triggered. you have to include in your macros the logic to address these states.

                              You should go look a the macros for Euclid Probe. We've been running this reliably for over 2 years at this point, both with fixed dock and moving bed pickups.

                              Also, we have found that inspecting the actual probe value is more reliable that checking the probe token in the object model. In the case of a mis-deploy, which is really rare with Euclid Probe, the probe value is more telling.

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