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

    5bar scara Problem configuring z probe using fsr switch

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    4
    98
    4.2k
    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.
    • fcwiltundefined
      fcwilt @gnmrc_
      last edited by

      @gnmrc_

      Here are the last three lines from the most recent homing code:

      G90
      G1 X0 Y0 F300 S2 ;move hotend to the center
      G30

      As I recall you said the S2 (which should be H2 according to the docs) is needed.

      But if the previous two G1 H1 commands worked the X and Y axis should be homed and the S2 (H2) should not be needed.

      Now the G30 is the probing command and it is not going to work since it needs the Z axis to be homed.

      And there is nothing in your homing file that tries to home the Z axis.

      To help clarify something try this, please:

      • remove the S2 from the last G1 command
      • remove the G30 command
      • test homing now

      Yes, I know that Z axis will not be homed but I am not worried about that.

      What worries me is the need for the S2.

      Thanks.

      Frederick

      Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

      gnmrc_undefined 1 Reply Last reply Reply Quote 0
      • gnmrc_undefined
        gnmrc_ @fcwilt
        last edited by

        @fcwilt I’ve done as you said, this is the error I get:
        G0/G1: insufficient axes homed

        fcwiltundefined 1 Reply Last reply Reply Quote 0
        • gnmrc_undefined
          gnmrc_ @Phaedrux
          last edited by

          @Phaedrux this is what I get from m122:

          m122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later
          Board ID: 0JD0M-9P6M2-NWNS0-7JKDD-3SN6S-1U0BJ
          Used output buffers: 1 of 26 (11 max)
          === RTOS ===
          Static ram: 23836
          Dynamic ram: 74172 of which 68 recycled
          Never used RAM 14004, free system stack 184 words
          Tasks: NETWORK(ready,13.4%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,84.1%,446) IDLE(ready,2.5%,30), total 100.0%
          Owned mutexes:
          === Platform ===
          Last reset 00:00:37 ago, cause: power up
          Last software reset at 2023-10-19 21:58, reason: User, GCodes spinning, available RAM 13692, slot 2
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Step timer max interval 0
          MCU temperature: min 29.8, current 33.2, max 33.4
          Supply voltage: min 12.5, current 12.5, max 12.6, under voltage events: 0, over voltage events: 0, power good: yes
          Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
          Events: 0 queued, 0 completed
          Driver 0: standstill, SG min n/a
          Driver 1: standstill, SG min n/a
          Driver 2: standstill, SG min n/a
          Driver 3: standstill, SG min n/a
          Driver 4: standstill, SG min n/a
          Driver 5:
          Driver 6:
          Driver 7:
          Driver 8:
          Driver 9:
          Driver 10:
          Driver 11:
          Date/time: 2023-10-24 17:39:02
          Cache data hit count 1374063136
          Slowest loop: 6.81ms; fastest: 0.18ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest read time 2.4ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
          === GCodes ===
          Segments left: 0
          Movement lock held by null
          HTTP is idle in state(s) 0
          Telnet is idle in state(s) 0
          File is idle in state(s) 0
          USB is idle in state(s) 0
          Aux is idle in state(s) 0
          Trigger is idle in state(s) 0
          Queue is idle in state(s) 0
          LCD is idle in state(s) 0
          Daemon is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty
          === Network ===
          Slowest loop: 15.77ms; fastest: 0.00ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
          HTTP sessions: 1 of 8
          = WiFi =
          Network state is active
          WiFi module is connected to access point
          Failed messages: pending 0, notready 0, noresp 0
          WiFi firmware version 1.23
          WiFi MAC address 98💿ac:20:cb:ca
          WiFi Vcc 3.37, reset reason Turned on by main processor
          WiFi flash size 4194304, free heap 25824
          WiFi IP address 192.168.178.109
          WiFi signal strength -54dBm, mode none, reconnections 0, sleep mode modem
          Clock register ffffffff
          Socket states: 0 0 0 0 0 0 0 0

          1 Reply Last reply Reply Quote 0
          • fcwiltundefined
            fcwilt @gnmrc_
            last edited by

            @gnmrc_ said in Problem configuring z probe using fsr switch:

            @fcwilt I’ve done as you said, this is the error I get:
            G0/G1: insufficient axes homed

            I should have asked - exactly what are you/it doing when this message appears - during the homing file execution?

            Thanks.

            Frederick

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

            gnmrc_undefined 1 Reply Last reply Reply Quote 0
            • gnmrc_undefined
              gnmrc_ @fcwilt
              last edited by gnmrc_

              @fcwilt It’does nothing the arm stays in his homed position

              Gianmarco

              fcwiltundefined 1 Reply Last reply Reply Quote 0
              • fcwiltundefined
                fcwilt @gnmrc_
                last edited by

                @gnmrc_ said in Problem configuring z probe using fsr switch:

                @fcwilt It’does nothing it stops the movement.

                When does that happen?

                When trying to execute the homing file?

                After that?

                Frederick

                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                gnmrc_undefined 1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  I assume you're working from this?

                  https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_five_bar_parallel_scara

                  Z-Bot CoreXY Build | Thingiverse Profile

                  gnmrc_undefined 1 Reply Last reply Reply Quote 1
                  • gnmrc_undefined
                    gnmrc_ @fcwilt
                    last edited by

                    @fcwilt, no the arm homes itself, then when it should do the x0 y0 move it stops

                    fcwiltundefined 1 Reply Last reply Reply Quote 0
                    • gnmrc_undefined
                      gnmrc_ @Phaedrux
                      last edited by

                      @Phaedrux yes, I’m using that and I used some other forum post from 2019 I think.

                      1 Reply Last reply Reply Quote 0
                      • fcwiltundefined
                        fcwilt @gnmrc_
                        last edited by

                        @gnmrc_ said in Problem configuring z probe using fsr switch:

                        Try to be more precise - I am not there seeing what you are seeing - need to help fill in the gaps of my knowledge. Thanks.

                        no the arm homes itself, then when it should do the x0 y0 move it stops

                        Are you referring to the move to X=0 Y=0 at the end of the homing file?

                        That is when you get the error message about un-homed axes?

                        Correct?

                        IF that is what is happening then the G1 H1 moves are NOT homing the axes. If they were being homed the move to X=0 Y=0 would work.

                        When a homing move fails, that is it reaches the end of the specified travel (in your case 200) without activating the endstop switch, there is no error message - it just stops moving and the axis is still not homed.

                        So remove the move to X=0 Y=0 (if it is still there), re-boot the machine and click on the HomeAll button in the DWC Dashboard.

                        Once the movement in both axes stops. check if the X and Y home buttons have changed to indicate they are homed.

                        Thanks.

                        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                        gnmrc_undefined 1 Reply Last reply Reply Quote 0
                        • gnmrc_undefined
                          gnmrc_ @fcwilt
                          last edited by

                          @fcwilt yes exactly, the machine stops before the x=0 y=0 move in the homing file, but I see from the board’s leds that my endstop gets triggered,I even tested with m119 ,and the arms stops when touching their relative endstops so I do not think this is the case.
                          Also if I only do the G1 H1 X and G1 H1 Y moves in the homing file when it ends my x and y axis results as homed.

                          Gianmarco

                          fcwiltundefined 1 Reply Last reply Reply Quote 0
                          • Phaedruxundefined
                            Phaedrux Moderator
                            last edited by

                            What are all the files in your system folder? It's not executing a different file than you expect is it?

                            Z-Bot CoreXY Build | Thingiverse Profile

                            gnmrc_undefined 1 Reply Last reply Reply Quote 0
                            • gnmrc_undefined
                              gnmrc_ @Phaedrux
                              last edited by gnmrc_

                              @Phaedrux no I checked, there is only 1 home5barscara.g

                              1 Reply Last reply Reply Quote 0
                              • fcwiltundefined
                                fcwilt @gnmrc_
                                last edited by

                                @gnmrc_ said in 5bar scara Problem configuring z probe using fsr switch:

                                @fcwilt yes exactly, the machine stops before the x=0 y=0 move in the homing file, but I see from the board’s leds that my endstop gets triggered,I even tested with m119 ,and the arms stops when touching their relative endstops so I do not think this is the case.
                                Also if I only do the G1 H1 X and G1 H1 Y moves in the homing file when it ends my x and y axis results as homed.

                                Gianmarco

                                Great, good to know. Thank you.

                                However I am still at a loss as to why the you cannot so a simple G90 followed by a plain G1 X0 Y0 unless...

                                OK, let's try this:

                                • create a HomeX.g file and put just the G91 G1 H1 X200 F300 commands in it
                                • create a HomeY.g file and put just the G91 G1 H1 Y200 F300 command sin it
                                • re-boot the machine
                                • click the Home X button and see if all goes well
                                • click the Home Y button and see if all goes well
                                • from the Console of the DWC execute an M208 and report back

                                Thanks very much.

                                Frederick

                                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                                gnmrc_undefined 1 Reply Last reply Reply Quote 0
                                • gnmrc_undefined
                                  gnmrc_ @fcwilt
                                  last edited by

                                  @fcwilt Yeah it’s really a frustrating situation….

                                  Ok I will try this solution and report back, but if I remember correctly it’s not possible to do an home X file and an home Y file, because reprap for a 5bar scara configuration during homing procedure will search and execute only a home5barscara.g, if this actually happens, I will create 2 macros home left and home right than put them in the homing file and see what happens.

                                  Thanks for the help,
                                  Gianmarco

                                  fcwiltundefined 1 Reply Last reply Reply Quote 0
                                  • Phaedruxundefined
                                    Phaedrux Moderator
                                    last edited by

                                    This thread is a bit long now. Can you create a summary post of the issue as it is currently and I can pass it along to DC42 to see if he has any suggestions.

                                    Z-Bot CoreXY Build | Thingiverse Profile

                                    gnmrc_undefined 2 Replies Last reply Reply Quote 0
                                    • fcwiltundefined
                                      fcwilt @gnmrc_
                                      last edited by

                                      @gnmrc_ said in 5bar scara Problem configuring z probe using fsr switch:

                                      @fcwilt Yeah it’s really a frustrating situation….

                                      Ok I will try this solution and report back, but if I remember correctly it’s not possible to do an home X file and an home Y file, because reprap for a 5bar scara configuration during homing procedure will search and execute only a home5barscara.g, if this actually happens, I will create 2 macros home left and home right than put them in the homing file and see what happens.

                                      Thanks for the help,
                                      Gianmarco

                                      Well if that is the case that you have to have the special file then I have no idea what might be going on.

                                      So just edit that one homing file and after the two G1 H1 commands add a M208.

                                      I want to know what the M208 "thinks" at that point.

                                      Thanks.

                                      Frederick

                                      Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                                      gnmrc_undefined 2 Replies Last reply Reply Quote 0
                                      • gnmrc_undefined
                                        gnmrc_ @Phaedrux
                                        last edited by

                                        @Phaedrux ok thanks so:

                                        I’ve built a 5bar scara arm, I can home the 2 arms in the home5barscara.g but when I try to do a G0/G1 move to set the hotend position to the center to home z, the arms overshoots the required position. If I only home the arms than send a G92 Z## the arm works as expected.

                                        In this thread there are also the config and homing files, plus the videos of the machine behaviour.

                                        Thanks for the help,
                                        Gianmarco.

                                        1 Reply Last reply Reply Quote 0
                                        • gnmrc_undefined
                                          gnmrc_ @fcwilt
                                          last edited by

                                          @fcwilt Ok, I’m going to report back asap.

                                          Thanks,
                                          Gianmarco

                                          1 Reply Last reply Reply Quote 0
                                          • gnmrc_undefined
                                            gnmrc_ @fcwilt
                                            last edited by

                                            @fcwilt so this is what I get from m208:

                                            g28
                                            Axis limits (mm)s X-162.7:250.0, Y-108.5:250.0, Z0.0:200.0
                                            Axis limits (mm)s X-162.7:250.0, Y-108.5:250.0, Z0.0:200.0
                                            Error: Failed to home axes Z

                                            Thanks for the help,
                                            Gianmarco

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