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

    strange "machine outside of limits" message

    Scheduled Pinned Locked Moved
    General Discussion
    4
    9
    312
    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.
    • gnydickundefined
      gnydick
      last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Firmware version?

        Are these errors during a tool change?

        Z-Bot CoreXY Build | Thingiverse Profile

        gnydickundefined 1 Reply Last reply Reply Quote 0
        • gnydickundefined
          gnydick @Phaedrux
          last edited by

          @Phaedrux yes, they are. I'm also getting them on homing calls, which I haven't touched in years.

          engikeneerundefined 1 Reply Last reply Reply Quote 0
          • engikeneerundefined
            engikeneer @gnydick
            last edited by

            @gnydick I'd suggest trying to give us a bit more information if you want some help. We're not mind readers!

            https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

            At the very least, I'd suggest providing:

            1. Firmware version
            2. Config, relevant homing and tool change files
            3. Steps to recreate

            You say it only happens after a fresh reboot. Does that mean only on the first tool pickup? What about when it happens from homing? Have you tried running each axis homing separately to see which is the offending axis?

            E3D TC with D3Mini and Toolboards.
            Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
            i3 clone with a bunch of mods

            gnydickundefined 3 Replies Last reply Reply Quote 1
            • gnydickundefined
              gnydick @engikeneer
              last edited by

              @engikeneer I think we're past the beginners post. This only started happening after updating to the latest firmeware, but you asked for it.

              Electronics
              Product Short Name Version
              Duet 3 MB6HC MB6HC 3.5.1
              Duet 3 Expansion TOOL1LC TOOL1LC 3.5.1
              Duet 3 Expansion TOOL1LC TOOL1LC 3.5.1
              Duet 3 Expansion TOOL1LC TOOL1LC 3.5.1
              Duet 3 Expansion TOOL1LC TOOL1LC 3.5.1
              Duet Software Framework DSF 3.5.1
              Duet Web Control DWC 3.5.1

              config.g config-override.g config-user.g homeall.g homec.g homex.g homey.g homez.g pause.g resume.g tfree0.g

              1 Reply Last reply Reply Quote 0
              • gnydickundefined
                gnydick @engikeneer
                last edited by

                @engikeneer tfree0.g tfree1.g tfree2.g tools.g tpost0.g tpost1.g tpost2.g tpre0.g tpre1.g tpre2.g

                1 Reply Last reply Reply Quote 0
                • gnydickundefined
                  gnydick @engikeneer
                  last edited by

                  @engikeneer I'm getting all sorts of weird behavior. I'm getting the pop stack aux() error also at random times.

                  Then my coordinates are off... sometimes. It's just a shit-show right now.

                  gloomyandyundefined 1 Reply Last reply Reply Quote 0
                  • gloomyandyundefined
                    gloomyandy @gnydick
                    last edited by

                    @gnydick Best to try and address each problem one at a time. The homing problem sounds like it may be the simplest to understand. So as above, can you come up with the minimum situation that triggers the problem? If you try homing each axis in turn when does the problem happen? What error message do you get. If that triggers the problem, do you still get the problem if you reboot the printer then just home the axis that caused the problem before?

                    gnydickundefined 1 Reply Last reply Reply Quote 0
                    • gnydickundefined
                      gnydick @gloomyandy
                      last edited by gnydick

                      @gloomyandy sorry, didn't mean to complicate things. I appreciate the effort. Please let me apologize ahead of time for the rant...

                      Ever since the last update, things have been wonky and it's hard to tell what symptom is distinct in cause from other symptoms.

                      The behavior isn't consistent either. I'm seeing the pop stack aux() error now on the PanelDue due to some command in the DWC, as opposed to when I tap a button on the PD. I'll be working from DWC for a while, then walk over to the machine and see it on the screen.

                      I can't come up with what triggers it. That's the problem. There are so many variables. And because it's a tool changer with sensor and button on the tool head itself, there is A LOT of logic spread all throughout to avoid crashes, clean the tools, temperature sensitive operations, eject, load.

                      I honestly don't have enough time to go through so many variables. I built a "platform" that is orchestrated well. One update later and I'm down 4 bent Obxidian revo nozzles $50/each, 3 PEI magnetic sheets gouged to hell, a dozen Z-axis lead screws bowed out from crashes, and the list just keeps growing.

                      Nothing in the changelog impacts any of my configuration.

                      These things are just supposed to work and supposedly are "validated" that the logic works.

                      I honestly expect somebody else to figure it out at this point, nobody specific, but Duet.

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