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

    Z-Probe sensor stuck at 1000

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    6
    17
    995
    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.
    • dc42undefined
      dc42 administrators @eyperry
      last edited by dc42

      @eyperry said in Z-Probe sensor stuck at 1000:

      Hi I am getting a permanent value of 1000 for the Z-probe sensor for my e3d toolchanger. Currently it is set at M558 P8 and I have tried changing the probe types to P1 and P5 but this did not change anything - I saw this worked for someone on the forum a while back. If I could get some help with this it would be appreciated. Thanks! Emma

      Most likely the Z probe switch is not connected correctly, or the M558 command in config.g is incorrect.

      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
      • eyperryundefined
        eyperry @kb58
        last edited by

        @kb58 Hi thank you for getting back to me. I have attached my config file below as well as photographs of the wiring of the toolchanger head. If you would be able to have a look and assist further it would be much appreciated. Thanks! Best, Emma

        ; Configuration file for Duet WiFi / Ethernet running RRF3 on E3D Tool Changer
        ; executed by the firmware on start-up

        ; General preferences
        M111 S0 ; Debugging off
        G21 ; Work in millimetres
        G90 ; Send absolute coordinates...
        M83 ; ...but relative extruder moves
        M555 P2 ; Set firmware compatibility to look like Marlin

        ; Network
        M550 P"ToolChanger" ; Set machine name
        ;M587 S"ssid" P"password" ; WiFi Settings
        ;M552 S1 P"ssid" ; Enable WiFi Networking
        M552 S1 ; Enable Networking
        M586 P0 S1 ; Enable HTTP
        M586 P1 S0 ; Disable FTP
        M586 P2 S0 ; Disable Telnet

        M667 S1 ; Select CoreXY mode

        ; Drive direction
        M569 P0 S0 ; Drive 0 X
        M569 P1 S0 ; Drive 1 Y
        M569 P2 S1 ; Drive 2 Z
        M569 P3 S0 ; Drive 3 E0
        M569 P4 S0 ; Drive 4 E1
        M569 P5 S1 ; Drive 5 E2
        M569 P6 S1 ; Drive 6 E3
        M569 P7 S0 ; Drive 7 COUPLER
        M569 P8 S0 ; Drive 8 UNUSED
        M569 P9 S0 ; Drive 9 UNUSED

        M584 X0 Y1 Z2 C7 E3:4:5:6 ; Apply custom drive mapping
        M208 X-35:328.5 Y-49:243 Z0:300 C0:500 ; Set axis maxima & minima
        M92 X100 Y100 Z1600 C200 E834:834:834:834 ; Set steps per mm assuming x16 microstepping
        M350 E16:16:16:16 I1 ; Configure microstepping with interpolation
        M350 C16 I10 ; Configure microstepping without interpolation
        M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation
        M566 X400 Y400 Z8 C2 E2:2:2:2 ; Set maximum instantaneous speed changes (mm/min)
        M203 X35000 Y35000 Z1200 C10000 E5000:5000:5000:5000 ; Set maximum speeds (mm/min)
        M201 X6000 Y6000 Z400 C500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2)
        M906 X1800 Y1800 Z1330 C400 I30 ; Idle motion motors to 30%
        M906 E1000:1000:1000:1000 I10 ; Idle extruder motors to 10%

        ; Endstops
        M574 X1 Y1 S3 ; Set X / Y endstop stall detection
        M574 Z0 ; No Z endstop
        M574 C1 S3 ; Stall detect coupler at low end of its range

        ; Z probe
        M558 P8 C"zstop" H3 F360 I0 T20000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
        G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
        M557 X10:290 Y20:180 S40 ; Define mesh grid

        ;Stall Detection
        M915 C S6 F0 H200 R4700 ; Coupler

        ;Stall Detection
        M915 X Y S3 F0 H400 R4700 ; X / Y Axes

        ; Heaters
        M308 S0 P"bedtemp" Y"thermistor" A"Bed" T100000 B4138 C0 ; Set thermistor
        M950 H0 C"bedheat" T0 ; Bed heater
        M143 H0 S225 ; Set temperature limit for heater 0 to 225C
        M140 H0 ; Bed heater is heater 0

        M308 S1 P"e0temp" Y"thermistor" A"T0" T100000 B4725 C7.06e-8 ; Set thermistor
        M950 H1 C"e0heat" T1 ; Extruder 1 heater
        M143 H1 S305 ; Set temperature limit for heater 1 to 300C

        M308 S2 P"e1temp" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 ; Set thermistor
        M950 H2 C"e1heat" T2 ; Extruder 2 heater
        M143 H2 S305 ; Set temperature limit for heater 2 to 300C

        M308 S3 P"e2temp" Y"thermistor" A"T2" T100000 B4725 C7.06e-8 ; Set thermistor
        M950 H3 C"duex.e2heat" T3 ; Extruder 3 heater
        M143 H3 S305 ; Set temperature limit for heater 3 to 300C

        ; M308 S4 P"e3temp" Y"thermistor" A"T3" T100000 B4725 C7.06e-8 ; Set thermistor
        ; M950 H4 C"duex.e3heat" T4 ; Extruder 4 heater
        ; M143 H4 S305 ; Set temperature limit for heater 4 to 300C

        ; Tools
        M563 P0 S"T0" D0 H1 F2 ; Define tool 0
        G10 P0 X0 Y0 Z0 ; Reset tool 0 axis offsets
        G10 P0 R0 S0 ; Reset initial tool 0 active and standby temperatures to 0C

        M563 P1 S"T1" D1 H2 F4 ; Define tool 1
        G10 P1 X0 Y0 Z0 ; Reset tool 1 axis offsets
        G10 P1 R0 S0 ; Reset initial tool 1 active and standby temperatures to 0C

        M563 P2 S"T2" D2 H3 F6 ; Define tool 2
        G10 P2 X0 Y0 Z0 ; Reset tool 2 axis offsets
        G10 P2 R0 S0 ; Reset initial tool 2 active and standby temperatures to 0C

        M563 P3 S"T3" D3 H4 F8 ; Define tool 3
        G10 P3 X0 Y0 Z0 ; Reset tool 3 axis offsets
        G10 P3 R0 S0 ; Reset initial tool 3 active and standby temperatures to 0C

        ; Fans
        M950 F1 C"fan1"
        M950 F2 C"fan2"
        M950 F3 C"duex.fan3"
        M950 F4 C"duex.fan4"
        M950 F5 C"duex.fan5"
        M950 F6 C"duex.fan6"
        M950 F7 C"duex.fan7"
        M950 F8 C"duex.fan8"

        M106 P1 S255 H1 T70 ; T0 HE
        M106 P2 S0 ; T0 PCF
        M106 P3 S255 H2 T70 ; T1 HE
        M106 P4 S0 ; T1 PCF
        M106 P5 S255 H3 T70 ; T2 HE
        M106 P6 S0 ; T2 PCF
        ; M106 P7 S255 H4 T70 ; T3 HE
        ; M106 P8 S0 ; T3 PCF

        M593 F50 ; cancel ringing at 50Hz (https://forum.e3d-online.com/threads/accelerometer-and-resonance-measurements-of-the-motion-system.3445/)
        ;M376 H15 ; bed compensation taper

        ;tool offsets
        ; !ESTIMATED! offsets for:
        ; V6-tool: X-9 Y39 Z-5
        ; Volcano-tool: X-9 Y39 Z-13.5
        ; Hemera-tool: X-37.5 Y43.5 Z-6

        G10 P0 X-9 Y39 Z-5.062 ; T0
        G10 P1 X-9 Y39 Z-5.039 ; T1
        G10 P2 X-9 Y39 Z-13.5 ; T2
        G10 P3 X-1.5 Y37.9 Z-38.21 ; T3
        ; ;;;;;;; Y40.4????

        ;deselect tools
        T-1

        ;M572 D0 S0.2 ; pressure advance T0
        ;M572 D1 S0.2 ; pressure advance T1
        ;M572 D2 S0.2 ; pressure advance T2
        ;M572 D3 S0.2 ; pressure advance T3

        M501; load config-override.g

        M98 P"/macros/define_glob.g"

        ; Added by Soph to create access point
        M98 P"accesspoint.g"
        undefined
        undefinedzstop3.jpg zstop2.jpg zstop1.jpg wiring.jpg toolchangerhead.jpg

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

          @eyperry your 3rd and 4th photos show the Z endstop LED is lit. Does it go out when you press the Z probe switch?

          If you run M98 P"config.g" do you get any error messages?

          If you send M558 without parameters, what is the response?

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

            Hi,

            Thank you for getting back to me.

            Yes the LED goes out when I press the z switch.

            When I ran M98 P"config.g" on YAT it seems to remove the access point I had kell5568 and changes it to DuetSSID which I cannot access as I do not have the network access key, but I get the below after disabling and renabling the Wifi.

            M552 S2
            ok<LF>WiFi module is providing access point kell5568, IP address 10.22.99.163<LF>

            M98P"config.g"
            Turn off the current WiFi mode before selecting a new one<LF>HTTP is enabled on port 80<LF>FTP is disabled<LF>TELNET is disabled<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>Warning: Macro file config-override.g not found.<LF>Warning: Macro file /macros/define_glob.g not found.<LF>WiFi module is idle<LF>ok<LF>WiFi module is providing access point DuetSSID, IP address 192.168.0.1<LF>

            M552 S0
            ok<LF>WiFi module is idle<LF>

            M98P"config.g"
            Error: Could not set WiFi hostname<LF>Failed to change WiFi mode (code -7)<LF>HTTP is enabled on port 80<LF>FTP is disabled<LF>TELNET is disabled<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>Warning: Macro file config-override.g not found.<LF>Warning: Macro file /macros/define_glob.g not found.<LF>M589: Failed to configure access point parameters<LF>Turn off the current WiFi mode before selecting a new one<LF>ok<LF>WiFi module started<LF>Error: Failed to initialise WiFi module, code -7<LF>

            M552 S2
            ok<LF>WiFi module started<LF>WiFi module is providing access point DuetSSID, IP address 192.168.0.1<LF>

            M98 P"config.g"
            Turn off the current WiFi mode before selecting a new one<LF>HTTP is enabled on port 80<LF>FTP is disabled<LF>TELNET is disabled<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M308 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>M950 command is not supported<LF>Warning: Macro file config-override.g not found.<LF>Warning: Macro file /macros/define_glob.g not found.<LF>WiFi module is idle<LF>ok<LF>WiFi module is providing access point DuetSSID, IP address 192.168.0.1<LF>

            When I send M558 i get:

            M558
            Z Probe type 8, input 0, invert no, dive height 3.0mm, probe speed 360mm/min, travel speed 20000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03<LF>ok<LF>

            Thanks again in advance for your help.

            Best,

            Emma

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

              I replied to your other thread describing how to update the firmware. Your config files are all formatted for RRF3+, but your installed firmware is still the older RRF2.05, so your config files as they are will not work. Best to follow the instructions I left in your other thread for updating the firmware. Then your config file errors will go away and you can get on with the setup.

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • eyperryundefined
                eyperry @eyperry
                last edited by

                @eyperry Hi, thank you so much for your help with the firmware update - it is finally now updated and the Z stop is working. I have however now run into another issue - do I need to post this as a new post? My issue is that now when I home the coupler C, it does not go into a horizontal position. When I run the Coupler-Lock macro the coupler is vertical as expected, but when I run Coupler-Unlock macro it is not horizontal. Would you be able to help? Thanks again in advance. Best, Emma

                I have attached images of the two positions below so you can see it is not horizontal.CouplerUnlock.jpg CouplerLock.jpg

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

                  Hi Emma, nice to see we have some lady engineers here.

                  When homing the coupler on my TC, it first turns to this position and stays there for a while because the homing command drives it in a clockwise direction for a while:

                  2021-08-19 17.11.41.jpg

                  Then it turns anticlockwise approx. 135 degrees to become horizontal.

                  Of the two photos you posted, which is the one it moves to initially when homing? Does it rotate anticlockwise in the next phase of the homing sequence? If it rotates clockwise then you need to swap one pair of the stepper motor phase wires, or reverse the direction in the M569 command for that driver.

                  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

                  eyperryundefined 1 Reply Last reply Reply Quote 0
                  • eyperryundefined
                    eyperry @dc42
                    last edited by

                    @dc42 Hi, thanks for getting back to me. When I press the Home C, it rotates clockwise to the same position as shown in your photograph, and then it rotates anticlockwise to the position in the first image I shared.

                    I only get the vertical position when I run the coupler lock macro. When I run the coupler unlock macro I get the same position as in the first image I shared again.

                    Thanks again for looking at this!

                    Best,

                    Emma

                    eyperryundefined 1 Reply Last reply Reply Quote 0
                    • eyperryundefined
                      eyperry @eyperry
                      last edited by

                      @eyperry Further to my previous message I note I was using the rrf3.x files. I tried also just now to use the rrf2.x files and I got a better result but the coupler unlock and lock positions are still slightly off centre (albeit better than before). I have attached photos of this below.

                      CouplerLock2.jpg CouplerUnlock2.jpg

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

                        @eyperry if the amount of movement was greatly wrong when using the RRF3 files then most likely the coupler steps/degree (M92) or microstepping (M350) was not set correctly.

                        I believe that it's normal to have to adjust the configuration files to correct for the coupler going to slightly the wrong position. My homec.h file contains this:

                        ; homec.g
                        ; called to home the C axis (coupler)

                        G91
                        M400
                        ;M913 C60 ; XY MOTORS TO 60% CURRENT
                        ;G1 H2 C30 F5000
                        ;M400
                        M913 C60 ; XY MOTORS TO 60% CURRENT
                        G1 H2 C-1000 F10000
                        G92 C-125
                        G90
                        M913 C100 ; XY MOTORS TO 100% CURRENT
                        G1 C0 F10000

                        ;Open Coupler
                        M98 P"/macros/Coupler - Unlock"

                        The G92 C125 line defines the coupler angle when it is fully clockwise. You can adjust the 125 figure to get it horizontal after the unlock macro runs.

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

                          Hi, thank you again for your help with this. It seems the issue was that the wrong angle was defined in the macro for the Coupler unlock - so it was calling it and rotating it to the wrong spot. I did some adjustments to the unlock macro and it seems to now home to the right spot! Thanks again for your help, it is much appreciated. Best, Emma

                          1 Reply Last reply Reply Quote 1
                          • Ritik126undefined
                            Ritik126
                            last edited by

                            Hello, I'm having a problem with my E3D tool changer's z-probe sensor, which is stuck at 1000. I also tried switching from IO to I1 and changing the wiring section, but nothing changed; it remained at 1000. I updated the reprap firmware to check and modify again, but the z-probe 1000 remained. I'd appreciate it if you could assist me with this. Thank you for your consideration! Raj, Ritik
                            *Herewith I'm attaching the image of my config.g and the Z-probe(web interface)!Screenshot 2022-09-04 155602.png Screenshot 2022-09-04 155637.png Screenshot 2022-09-04 155655.png

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

                              @ritik126 Please start a new thread.

                              Z-Bot CoreXY Build | Thingiverse Profile

                              Ritik126undefined 1 Reply Last reply Reply Quote 0
                              • Ritik126undefined
                                Ritik126 @Phaedrux
                                last edited by

                                @phaedrux Thank you for your response but can you please elaborate this!

                                Rushmere3Dundefined 1 Reply Last reply Reply Quote 0
                                • Rushmere3Dundefined
                                  Rushmere3D @Ritik126
                                  last edited by Rushmere3D

                                  @ritik126 Start a new topic of your own from the main page of the forum.

                                  And then follow this for info required.
                                  https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

                                  Follow my adventures in 3D Printing, laser cutting and electronics. https://linktr.ee/Rushmere3D

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