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

Precision Piezo Orion always triggered

Scheduled Pinned Locked Moved
Third-party add-ons
3
4
332
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
    LostJen
    last edited by 7 Jun 2020, 20:30

    My Orion V2.0 on a Duet Maestro connected to an Ender 3Pro used to work fine. Red normally moving to blue when tapped. That was reflected in WebUI as 0 and 1000.

    I took the printer apart and made some major changes (direct drive for my Bondtech and V6 (with the heatsink inside the bondtech), linear rails on X and Y, and dual Z with a second fine pitched screw) and then while I was restarting it I upgraded from 3.0 to 3.11.

    Now no matter what gcode I use I always get backward results in the web UI. I've tried zprobe.in and ^zprobe.in as well as I1, nothing, I0, and I2 for a lark. The lights are still correct. I even had a spare orion board and switched it out and those are also correct, but no matter what settings I get 1000 and only 0 when pressing. This is nonfunctional since I can't start a probe triggered.

    Here is the base gcode that the ^ and I1 are being added to with no changes in the web UI being wrong or the sensor showing the correct state.
    M558 P8 C"zprobe.in" R0.5 F200 ;this has tried all kinds of tweaks
    G31 X0 Y0 Z-0.1 P100 ;this is unchanged from when it worked

    I've triple checked the wiring with a meter for both shorts between and within each of the three wires. I'm using the maestro zprobe port with 1 [in] = Green, [gnd] 2 = black, and 3 [3.3v] red. The piezo is connected from inner to outer as RBG (based on the print on the board that says V+ GND Sig.

    Based on my understanding ^zprobe_in and zprobe_in should flip between the 0 and 1000 but they are not. Given I used two different Orion boards is something wrong with my Maestro? I did see a few posts where people say they had to switch ground and signal different from the documentation.

    "I try to meditate, cause they told me it'll help
    But the last thing I need is more time alone inside myself"
    Hollow by Icon For Hire
    http://www.youtube.com/watch?v=9mSf_i1U0TI

    1 Reply Last reply Reply Quote 0
    • undefined
      Phaedrux Moderator
      last edited by 7 Jun 2020, 20:34

      !zprobe.in

      The exclamation mark inverts.

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • undefined
        DaveA
        last edited by 8 Jun 2020, 10:53

        I put a V2 Orion on my old Folgertech I3 with a Maestro a few weeks ago and it's working great. So much better than the BLTouch. However, I'm using the analog output of the Orion rather than digital. Reading the Orion doc. it just seemed easier to use analog and not have to fiddle with the pot.

        My Orion entries in config.g:
        ; Z-Probe (Piezo Orion)
        M558 P1 C"^zprobe.in" H5 R0.1 F1200 T3600

        ;Piezo Orion
        G31 P540 X0 Y0 Z-.12 ; Set Z probe trigger value, offset and trigger height

        1 Reply Last reply Reply Quote 0
        • undefined
          LostJen
          last edited by 8 Jun 2020, 15:02

          Sorry everyone I wasn’t getting email notifications. I have never actually seen a ! In a command but ^ was common. The dozuki has this example M558 P9 C"^zprobe.in" H5 F100 T2000.

          So ^ is pull-up regardless of value and ! Is invert. Ok.

          So I’m betting that 3.0 let me use I1 but I have to use ! In 3.11

          Thanks.

          "I try to meditate, cause they told me it'll help
          But the last thing I need is more time alone inside myself"
          Hollow by Icon For Hire
          http://www.youtube.com/watch?v=9mSf_i1U0TI

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