Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Smart effector not triggering on G30

    Duet Hardware and wiring
    4
    22
    867
    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.
    • Stoop
      Stoop last edited by

      unplugging 8 way cable returns 1000

      dc42 1 Reply Last reply Reply Quote 0
      • aidar
        aidar last edited by aidar

        P parameter in G31 is p in your config. Shouldnt it be P ? I mean capital letter or how you call it in english...

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

          @stoop said in Smart effector not triggering on G30:

          unplugging 8 way cable returns 1000

          Check the underside of the Smart Effector for a solder bridge between the pins of the 8-way connector.

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

            4k ohms between zprobe in and gnd on duet (tested from 8-way plug)

            Aidar, changed, I'll test. I think duet handles this though.

            1 Reply Last reply Reply Quote 0
            • Stoop
              Stoop last edited by

              no solder bridge. nothing reading as a short anyway.

              1 Reply Last reply Reply Quote 0
              • Stoop
                Stoop last edited by

                Aidar - No change after capitalization.

                1 Reply Last reply Reply Quote 0
                • Stoop
                  Stoop last edited by

                  DC42 - Is there any way to log the zprobe hit? like can I just put a LED between 2 pins and see if it blinks?
                  I also can hook up my oscilliscope if I know what I'm looking for.

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

                    @stoop, yes you can connect an LED between output and ground.

                    The schematic is is at https://github.com/T3P3/SmartEffector/blob/master/SmartEffector/SmartEffector_v1.3/SmartEffector_Schematic_v1.3.pdf. You will see that same pin of the attiny MCU drives the LED through a 150 ohm resistor, and the output pin through a 1K resistor. If the 1K resistor was open circuit then you would get a Z probe reading of 1000 all the time because of the pullup resistor in the Duet.

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

                      @dc42 I get a v+(3,3?) blip on z_probe_in on the duet wifi board when I tap the hot end.

                      So, either Duet wifi board, or config is wrong.
                      How can I see what the firmware is seeing?

                      Can I run the Z_Probe_in to somewhere else?

                      1 Reply Last reply Reply Quote 0
                      • Stoop
                        Stoop last edited by

                        Maybe I'll start the config.g from scratch.. But you see what I have there, nothing misconfigured?

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

                          @stoop said in Smart effector not triggering on G30:

                          M558 P5 R0.4 H5 F1200 T6000 ; Set Z probe type to switch and the dive height + speeds

                          Please send M558 without parameters, and check that the values it reports match those values in config.g. Also send G31 T5 to check that the G31 parameters are correct.

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

                            M558
                            Z Probe type 5, invert no, dive height 5.0mm, probe speed 1200mm/min, travel speed 6000mm/min, recovery time 0.40 sec, heaters normal, max taps 1, max diff 0.03

                            G31 T5
                            Threshold 100, trigger height -0.10, offsets X0.0 Y0.0

                            1 Reply Last reply Reply Quote 0
                            • Stoop
                              Stoop last edited by

                              Ok, Been farting around.
                              When I tap the hot-end, the Zprobe on the web interface DOES go to 1000.
                              But it doesn't stop diving on the G30.

                              What the heck?

                              I just re-updated the firmware to the latest 2.02
                              Same thing.

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

                                Most strange:

                                • You have verified that you are getting a 3.3v pulse on that signal
                                • If you disconnect the Smart Effector from the Z probe input, the Z probe reading changes from 0 to 1000, so the Z probe input is working

                                You could try using P8 instead of P5 in the M558 command to get a faster response; but the pulse should be plenty long enough for P5 to work too.

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

                                  Yes, I can SEE the pulse on the web interface, I can't imagine its not long enough, but I'll try that now.
                                  I USED to have a mechanical z-probe, is there some other setting I might have changed?

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

                                    Please confirm that this is the test you are doing:

                                    • Position the effector well above the bed.
                                    • Send G30. [Printer must previously have been homed.]
                                    • Effector moves towards the bed
                                    • Tap the nozzle upwards
                                    • The green LED on the effector should flash, and the downward movement should stop at the same 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
                                    • Stoop
                                      Stoop last edited by

                                      Well, I deleted my config.g override, and changed to p8. It stopped travel.
                                      Changed back to p5, seems to be working now.
                                      Odd, nothing in the config override should have been doing anything, but it seems to be working now.
                                      Thanks for all your help @dc42

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