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

    Z Probe - Omron PNP inductive sensor

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    17
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      What type of printer is it? There is a known bug with homing SCARA printers in some firmware versions.

      If your printer isn't a SCARA, try sending the same commands that are in homez.g manually, one at a time.

      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
      • lassivvundefined
        lassivv
        last edited by lassivv

        Have Prusa i2 printer, totally worked ok with Ramps/Re-arm compination years. Normal cartesian printer.

        Sended that homez.file commands one at a time via g-code console.

        19.01.21 G30
        Error: G0/G1: insufficient axes homed
        19.01.15 G1 X15 Y25 F2000
        19.01.06 G90
        19.00.59 G1 Z5 F600 S2
        19.00.35 G91

        Everything else going ok, but that G30 gives that same error immediately when i send that to printer.

        edit: G28 gives same "Error: G0/G1: insufficient axes homed" error.

        edit2: One more screenshot if that tells something more:
        0_1544291089266_23d822a2-dfca-457a-8ad7-0b9882e30e4b-image.png

        Is this P5 right choice Z probe when i have this PNP induction digital sensor (with 10k resistor signal to ground). ( P5 (from RepRapFirmware 1.14) selects a switch by default (normally closed) for bed probing between the In and Gnd pins of the Z-probe connector (Duet 0.8.5 and Duet 2 WiFi).)

        Hopefully someone have tips. I dont get any ideas what i can try to get this working 😞

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

          Do you have any deployprobe.g or retractprobe.g files that you didn't create yourself? If so, delete them.

          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

          lassivvundefined 1 Reply Last reply Reply Quote 0
          • lassivvundefined
            lassivv
            last edited by lassivv

            Just do my install with this tutorial, nothing more do yet.
            https://duet3d.dozuki.com/Guide/3.)+Configuration+(General+Cartesian)/10

            This files are generated that reprapconfigutator tool.

            retractprobe.g
            ; generated by RepRapFirmware Configuration Tool v2 on Sat Dec 08 2018 14:23:46 GMT+0200 (Itä-Euroopan normaaliaika)
            M564 S0 ; don't apply limits
            G1 Z40 F10000 ; raise head
            G1 X-59 Y66 Z35 ; move over the post
            G1 Z7 F500 ; push probe down on post
            G1 Z35 F10000 ; raise head again
            G1 X0 Y0 ; move to somewhere sensible
            M564 S1 ; apply limits again

            ; deployprobe.g
            ; called to deploy a physical Z probe
            ;
            ; generated by RepRapFirmware Configuration Tool v2 on Sat Dec 08 2018 14:23:46 GMT+0200 (Itä-Euroopan normaaliaika)
            M564 S0 ; don't apply limits
            G1 X25 Y93 Z40 F10000 ; put probe arm next to belt
            G1 X-5 F500 ; move probe arm across belt
            G1 X12 F1000 ; move probe back
            G1 X0 Y0 F10000 ; move to somewhere sensible
            M564 S1 ; apply limits again


            Is possible there is some more axles or something why that say "G0/G1: insufficient axes homed". Hard to find that problem because that not saying anything more than "insufficient axes homed", is there any place of web control or memory card where is going more exact log, where can find solution of this?

            Not understand what can be wrong. All axis moving ok, if i put g-code console: M564 S0 H0. Then every axis goes ok both directions. All limit switch give (hit endpoint) yes, when i push limit switches, same thing when put something metal near to z probe. All axis move out to limit switch if drive + numbers to millimeters, if but - millimeters axis goes nearer to limit switch.

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

              OK, I guess you checked the "Deploy/Retract probe" box. Please delete those files, and if you run the configurator again don't check that box.

              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
              • lassivvundefined
                lassivv
                last edited by lassivv

                Many thanks probing start to work and now all axis home ok. Many many thanks to you @dc42

                Tomorrow need to try setup probe offset. And try to know more better what is best choice to pick up bed leveling system. My old system do before everyprint 3point measuring on bed.

                If some link or recommeded tips i take all gladly 🙂

                Think to start with this links:
                https://duet3d.dozuki.com/Wiki/Setting_up_automatic_probing_of_the_print_bed
                https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

                Only thing dont know if these Y 40mm offset or is that -40mm, but maybe can try that tomorrow and be ready to click emernency button 🙂
                0_1544303297515_4ae96872-109a-4d57-9d80-57540ec93fb5-image.png

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

                  The probe offset is measured from the head reference point (which is normally the nozzle) to the probe.

                  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
                  • lassivvundefined
                    lassivv
                    last edited by

                    Thanks for info. Printer works like a charm now, first test parts printed without any problems and quality is very nice and steppers works very smoothie, i think because this awesome stepper drivers.


                    One weird "problem" is on inside web control, when printing is going. First layer status seems calculate right.

                    But after that whole print layer is sitting 2/10layers.

                    Example pictures. Part is about 70% ready like progression bar tells, but Layer is 2/10 like see picture.
                    0_1544369897492_4e7284e2-490d-48fb-8374-0c108c02647e-image.png

                    Then wait little bit and progression bar goes ready(100% like screenshot (inside screenshot printer is still printing), still print continue about 2minutes and after that printer shutdown right way what i programmed on end g code.
                    0_1544369908929_9ddc72ba-4fd5-4ee8-8be0-8dbfd56e20f2-image.png

                    Parts printed ok, but some problem on that layer status or something.

                    Here is gcode what is used to test and get that error. I use Prusa Slic3r.
                    0_1544369755571_Part Studio 7 - Part 1petg.gcode

                    Here my start gcode and stop gcode what i give on Slic3r start and stop gcode fields like my older printers.

                    Start code:
                    M80 ; virtalähde päälle
                    T0 ; Tool valinta
                    G90 ;absolute positioning
                    M83 ; extruder relative mode
                    M104 S[first_layer_temperature] ; set extruder temp
                    M140 S[first_layer_bed_temperature] ; set bed temp
                    ; Homing & leveling
                    G28 ; Home all axis M80 ; virtalähde päälle
                    G1 X95 Y95 F4000 ; Go to bed center before probing
                    ;Wait for Temperature
                    M109 S[first_layer_temperature] ; wait for extruder temp
                    M190 S[first_layer_bed_temperature] ; wait for bed temp
                    G30 ; Find the Z=0
                    G29 S1 ; Load the height map from the last time I used G29 to probe the bed.
                    ;Print intro line
                    G1 Y193 F1000.0 ; go outside print area
                    G92 E0.0 ; reset extruder

                    Stop code
                    M104 S0 ; turn off temperature
                    M140 S0 ; Turn off bed
                    G1 X100 ; 100 X axis
                    G1 Y100 ; 100 Y axis
                    M84 ; disable motors

                    1 Reply Last reply Reply Quote 0
                    • lassivvundefined
                      lassivv
                      last edited by lassivv

                      I updated newer version that slic3r and that seems to solve that problem. Now just need to start learning everything what is possible with Duet. Big thanks fast help.

                      p.s. Now just waiting when i get my PanelDue 7" and hope get that working 🙂

                      1 Reply Last reply Reply Quote 0
                      • lassivvundefined
                        lassivv @dc42
                        last edited by lassivv

                        @dc42 said in Z Probe - Omron PNP inductive sensor:

                        Do you have any deployprobe.g or retractprobe.g files that you didn't create yourself? If so, delete them.

                        One question related to that. Printer works very good and new 7" PanelDue works perfect.

                        Console gives every print error (web control and paneldue):
                        Warning: Macro file deployprobe.g not found.
                        Warning: Macro file rectractprobe.g not found.

                        Print goes ok, but want that warning pop-ups disappier. Can i modify config or some file that kind not get that errors with that two files what i deleted.

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

                          I think you have debugging enabled, otherwise you would not get those messages. If you have a M111 command in config.g then it should read: M111 S0

                          You could also create new deployprobe.g and retractprobe.g files that contain just a comment line such as:

                          ; Empty file
                          

                          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
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA