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

    IR Probe setup problems

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    8
    20
    2.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.
    • wannathermalundefined
      wannathermal
      last edited by

      Fixed! Once again I muddled through the documentation 5 times to get it right!

      1 Reply Last reply Reply Quote 0
      • aparkinundefined
        aparkin
        last edited by

        yes i find the documentation is not well written are organized i.e start reading this page go to that page come back to this page before you know it you have 20 tabs open and you lost some bit that you need …..... if your doing bed mesh next i found a great right up here

        https://forum.e3d-online.com/index.php?threads/my-guide-to-duet-mesh-auto-leveling.2456/

        1 Reply Last reply Reply Quote 0
        • wannathermalundefined
          wannathermal
          last edited by

          Well, I have to disagree. I think the docs are fine it is just me having trouble outing it all into practice.

          1 Reply Last reply Reply Quote 0
          • inachisiojexusundefined
            inachisiojexus
            last edited by

            I'm having the same issue of trigger going from 1 to 1000. Could you share how you fixed this?

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

              If it's giving a reading of 1 when not triggered and 1000 when triggered and the red LED on the IR sensor is lit, then there are a couple of possible causes:

              1. Sensor starting up in digital mode instead of analog mode. How many flashes does it give when you power it up? Have you specified type 1 (P1) in your M558 command?

              2. Very strong background IR, for example direct bright sunlight (no clouds) reflecting off the bed into the sensor.

              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
              • inachisiojexusundefined
                inachisiojexus
                last edited by

                The sensor flashed two times on power-up (USB). I had sent the M558 P1 via DWC, following the instructions here: https://miscsolutions.wordpress.com/mini-height-sensor-board/

                I proceeded to power the board from 24V and did the exact same steps (M558 P1, G31 P500 Z1.0) and for whatever reason I started getting correct readings from the probe.

                Next I ran Auto Delta Calibration and got a bunch of "Error: Z probe already triggered at start of probing move", but after a bit of scratching my head I increased the M558 H parameter from 2 to 5, and it went through neatly.

                One more question:

                I ran the calibration three times:

                1.52.25 G32
                Calibrated 3 factors using 7 points, deviation before 0.240 after 0.240
                1.51.24 G32
                Calibrated 3 factors using 7 points, deviation before 0.252 after 0.244
                1.43.36 G32
                Calibrated 3 factors using 7 points, deviation before 1.740 after 0.257
                

                I have no idea how to interpret the numbers. Is this something to worry about? I have a fair 0.5mm (or so) deep cavity in the center of my heatbed from when I went looking for oil down there (in all seriousness, I tweaked some slicer settings when I had no clue what I was doing). It runs through the black low-friction surface material up until the glass bed, latter of which luckily looks undamaged. Aside from the drilled hole right at my X0 Y0 Z0, I wonder if the irregular surface on top of the glass could pose a problem for the IR probe… I've been considering peeling it off anyway after giving it hell in a multitude of creative ways on more than one occasion.

                M665
                Diagonal 397.107, delta radius 157.000, homed height 523.378, bed radius 160.0, X 0.000°, Y 0.000°, Z 0.000°
                
                M666
                Endstop adjustments X-1.04 Y0.55 Z0.48, tilt X0.00% Y0.00%
                
                1 Reply Last reply Reply Quote 0
                • number40fanundefined
                  number40fan
                  last edited by

                  inachisiojexus, try running the calibration with a factor of 9 and post your M665 and M666 after it is done. Make sure bed compensation is disabled if you don't already have that in your bed.g.

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

                    The M558 P1 command needs to be in config.g so that the pullup resistor is already disabled 4 seconds after power up, which is when the sensor checks for it and decides which more to operate in.

                    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
                    • inachisiojexusundefined
                      inachisiojexus
                      last edited by

                      @number40fan:

                      inachisiojexus, try running the calibration with a factor of 9 and post your M665 and M666 after it is done. Make sure bed compensation is disabled if you don't already have that in your bed.g.

                      I couldn't figure out how to do that… Do I need to write in the probe points by hand, and if so, how should I calculate them? My bed.g currently has seven probe points:

                      ; bed.g
                      G28
                      M561
                      M98 Pdeployprobe.g
                      G30 P0 X0 Y129.9 H0 Z-99999
                      G30 P1 X112.5 Y64.95 H0 Z-99999
                      G30 P2 X112.5 Y-64.95 H0 Z-99999
                      G30 P3 X0 Y-129.9 H0 Z-99999
                      G30 P4 X-112.5 Y-64.95 H0 Z-99999
                      G30 P5 X-112.5 Y64.95 H0 Z-99999
                      G30 P6 X0 Y0 H0 Z-99999 S9
                      M98 Pretractprobe.g
                      G1 X0 Y0 Z150 F15000
                      
                      1 Reply Last reply Reply Quote 0
                      • inachisiojexusundefined
                        inachisiojexus
                        last edited by

                        @dc42:

                        The M558 P1 command needs to be in config.g so that the pullup resistor is already disabled 4 seconds after power up, which is when the sensor checks for it and decides which more to operate in.

                        I thought I didn't change any configs between testing on USB and 24V, but had I done that, that would explain the behavior. Looks like I read the instructions too hastily - my bad! Thanks for the clarification.

                        1 Reply Last reply Reply Quote 0
                        • number40fanundefined
                          number40fan
                          last edited by

                          Your bed.g already has the S9 (9 factor) already in it. You should comment out the M98 since you don't have a deployable probe. Then just click on the Auto Calibration.

                          1 Reply Last reply Reply Quote 0
                          • inachisiojexusundefined
                            inachisiojexus
                            last edited by

                            I just changed it from 3 to 9 to do the 9-factor calibration as you requested. However, DWC console says I need 9 probing points for 9-factor calibration, and I'm clueless about the theory behind the probing procedure and what the firmware might expect, and consequently the proper conventions regarding constructing the grid. Is there a general explanation that you could direct me to study?

                            Apologies if my questions are too elementary. I appreciate the babysitting and hope that I get the opportunity to pass on the knowledge to the next rookie. 🙂

                            1 Reply Last reply Reply Quote 0
                            • Dougal1957undefined
                              Dougal1957
                              last edited by

                              go to http://www.escher3d.com/pages/wizards/wizardbed.php put in the figures for your printer ie 10 or 13 probe points (6 periphery and 3 or 6 midpoints) the radius of your bed and set it for 6 factors (Then modify the resultant file to make it S8 rather than 6 or 9 and try again

                              1 Reply Last reply Reply Quote 0
                              • inachisiojexusundefined
                                inachisiojexus
                                last edited by

                                Cheers Dougal1957.

                                S9:

                                1.00.25 M666
                                Endstop adjustments X0.56 Y3.85 Z-4.41, tilt X0.72% Y-3.38%
                                1.00.22 M665
                                Diagonal 402.182, delta radius 156.490, homed height 523.115, bed radius 160.0, X -1.838°, Y 0.187°, Z 0.000°
                                1.00.09 G32
                                Calibrated 9 factors using 10 points, deviation before 0.276 after 0.063
                                

                                S8:

                                1.04.48 M666
                                Endstop adjustments X2.17 Y2.71 Z-4.88, tilt X-0.29% Y-3.65%
                                1.04.37 M665
                                Diagonal 402.182, delta radius 156.697, homed height 523.175, bed radius 160.0, X -1.383°, Y 0.514°, Z 0.000°
                                1.04.19 G32
                                Calibrated 8 factors using 10 points, deviation before 0.070 after 0.022
                                

                                Run in succession. Coordinates read {-3.7 -1.1 155.73} after calibration finishes.

                                S8:

                                1.40.41 M666
                                Endstop adjustments X1.22 Y3.60 Z-4.82, tilt X0.33% Y-3.54%
                                1.40.23 M665
                                Diagonal 402.182, delta radius 157.024, homed height 523.242, bed radius 160.0, X -1.255°, Y -0.003°, Z 0.000°
                                1.40.08 G32
                                Calibrated 8 factors using 10 points, deviation before 0.130 after 0.056
                                

                                Head position reported by DWC: {2.5 0.1 155.78}

                                Configs:

                                ; bed.g file for RepRapFirmware, generated by Escher3D calculator
                                ; 10 points, 6 factors, probing radius: 150, probe offset (0, 25)
                                
                                G28
                                M561
                                G30 P0 X0.00 Y128.57 Z-99999 H0
                                G30 P1 X118.86 Y68.62 Z-99999 H0
                                G30 P2 X129.90 Y-75.00 Z-99999 H0
                                G30 P3 X0.00 Y-150.00 Z-99999 H0
                                G30 P4 X-129.90 Y-75.00 Z-99999 H0
                                G30 P5 X-118.86 Y68.62 Z-99999 H0
                                G30 P6 X0.00 Y56.25 Z-99999 H0
                                G30 P7 X64.95 Y-37.50 Z-99999 H0
                                G30 P8 X-64.95 Y-37.50 Z-99999 H0
                                G30 P9 X0 Y0 Z-99999 S8
                                
                                G1 X0 Y0 Z150 F15000
                                
                                
                                ; config.g
                                
                                M111 S0
                                G21
                                G90
                                M83
                                M555 P1
                                M665 R157 L397.1073 B150 H525
                                M666 X0 Y0 Z0 
                                M208 Z0 S1
                                
                                ; config-override.g
                                ; This is a system-generated file - do not edit
                                ; Delta parameters
                                M665 L397.1073 R157.000 H523.395 B160.0 X0.000 Y0.000 Z0.000
                                M666 X-1.058 Y0.551 Z0.507 A0.00 B0.00
                                ; Heater model parameters
                                M307 H0 A90.0 C700.0 D10.0 S1.00 B1
                                M301 H0 P10.0 I0.100 D200.0
                                M307 H1 A455.7 C314.0 D7.0 S1.00 B0
                                M307 H2 A340.0 C140.0 D5.5 S1.00 B0
                                M307 H4 A340.0 C140.0 D5.5 S1.00 B0
                                M307 H5 A340.0 C140.0 D5.5 S1.00 B0
                                M307 H6 A340.0 C140.0 D5.5 S1.00 B0
                                M307 H7 A340.0 C140.0 D5.5 S1.00 B0
                                ; Z probe parameters
                                G31 T1 P500 X0.0 Y0.0 Z0.70
                                G31 T3 P500 X0.0 Y0.0 Z0.70
                                G31 T4 P25 X0.0 Y0.0 Z11.30
                                

                                Sorry about some garbage leftover I've neglected to clean (like that deployprobe.g call from my preceding setup with BLTouch - I'm sure there's more).

                                EDIT: I tried adjusting the rod length from 397.1073 (manufacturer default) to 396.6 (not that precisely measured by myself), not sure whether it was for better or worse, so I changed it back. Now I'm noticing that when I home all axes, after the head moves down the last time the effector shifts horizontally. Is that due to successful or unsuccessful calibration, or my tweaking of dimensions parameters?

                                EDIT2: Did one more S8 round.

                                P.s. I realize we're way off-topic now… Just wouldn't make sense to create a new thread at this point.

                                1 Reply Last reply Reply Quote 0
                                • inachisiojexusundefined
                                  inachisiojexus
                                  last edited by

                                  Well… I had no luck calibrating the printer properly. That is, until during bed mesh generation the nozzle crashed into the bed and DWC said that the probe was not triggered during a probing move, which led to the realization that the wiring was loose and the probe would lose power randomly during movements. I fixed the wiring and ran a 6-factor auto-calibration and it appears I'm currently getting decent accuracy at least on the XY-plane.

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