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

Bed not stopping after Piezo Orion has triggered

Scheduled Pinned Locked Moved
General Discussion
4
8
839
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
    Royce
    last edited by Royce 3 Jun 2019, 21:38 6 Mar 2019, 20:41

    Hi folks,
    I'm experiencing an intermittent issue with my Duet equipped Hypercube Evo.
    After the last print worked fine, the Duet doesnt seem to recognize the Orion trigger signal and moved the bed into the nozzle. The LED turns blue and the Z-Probe value in DWC turns to 1000 but the bed doesnt stop.
    It can be seen here:
    https://www.youtube.com/watch?v=QPJLcA02j2s

    Here's a pastebin of my config (which worked fine before):
    https://pastebin.com/SvTHw5F2

    I already talked to Idris and measured the signal voltage of the Orion which was fine.
    I also went through the usual procedure with loosening the orion mount screws etc.
    What also makes me wonder is that the Z value is the following after the bed is stopping (when it pressed the entire assembly up for about 5-10mm):
    alt text

    Any help is appreciated!

    Best,
    Paul

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 7 Mar 2019, 11:56

      M558 P8 I1 R1 H5 F480
      G31 X0 Y0 Z-0.05 P100 ; Set Z probe trigger value, offset and trigger height

      If the Orion produces a negative-going trigger, then those values look OK to me.

      Are you sure that you are consistently getting a reading of 1000 when the probe triggers, and the problem isn't a bad connection between the output of the Orion and the Duet? With a probe that produces a negative going signal (i1 in the M558 command), a disconnected output wire looks the same to the Duet as a probe that is not triggered.

      Also try running M558 without parameters form the console, to check that the values you set in config.g haven't been overridden. Similarly, check the G31 values by sending G31 T8.

      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
      • undefined
        Moriquendi
        last edited by 7 Mar 2019, 18:54

        The output of the Orion is active low.

        Paul and I went through all the trouble shooting steps I could think of last night. He measured voltages of 3.233 untriggered and 0v triggered. This is at the Orion end of the cable, however, since the Orion uses an open drain output, a broken cable would result in a floating pin that normally measures ~0.5v. He also tried with three different cables.

        What's really puzzling to me is what's shown in the video, the Orion triggers lighting the blue LED but the bed keeps moving. If there were an issue with the sensitivity of the Orion or its triggering then I would expect to see the bed hit the nozzle, keep moving, and then have the Orion trigger. It appears that the Duets response to the trigger signal is delayed for some reason.

        Idris

        1 Reply Last reply Reply Quote 0
        • undefined
          Royce
          last edited by Royce 3 Jul 2019, 18:59 7 Mar 2019, 18:57

          Thanks for the answer!
          Yes, the Orion is indeed produing a active-low trigger, as clarified with Idris.
          I'm getting a value of 1000 whenever the probe / nozzle is tapped on. The connection between the Orion and the board is fine, i double checked that with 3 other spare cables.
          Here's the output of M558, looks good to me:
          alt text
          and of G31 T8:
          alt text

          Best,
          Paul

          1 Reply Last reply Reply Quote 0
          • undefined
            NicoLab28
            last edited by 7 Mar 2019, 19:05

            My config that works, for orion precision piezo:

            M558 P5 I1 R0.4 F300 X0 Y0 Z0
            G31 X0 Y0 Z-0.0 P10

            1 Reply Last reply Reply Quote 0
            • undefined
              Royce
              last edited by 10 Mar 2019, 12:02

              Any ideas on this issue?

              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators
                last edited by 18 Mar 2019, 17:53

                Bad connection in the output pin of the cable?

                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

                undefined 1 Reply Last reply 1 Apr 2019, 17:41 Reply Quote 0
                • undefined
                  Royce @dc42
                  last edited by 1 Apr 2019, 17:41

                  @dc42
                  I tried with 3 different cables with no luck.
                  In the meantime, Idris sent me a replacement Orion, I'm going to check this soon and report back

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