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

    Z Probe Error

    Scheduled Pinned Locked Moved Unsolved
    General Discussion
    3
    12
    360
    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.
    • oneearthtechundefined
      oneearthtech
      last edited by

      hey @baird1fa

      Yes the Printer home ok from what I can tell.

      Sure here they are below:

      bed.g

      G28
      G30 P0 X0.00 Y165.00 Z-99999 H0
      G30 P1 X106.06 Y126.40 Z-99999 H0
      G30 P2 X162.49 Y28.65 Z-99999 H0
      G30 P3 X142.89 Y-82.50 Z-99999 H0
      G30 P4 X56.43 Y-155.05 Z-99999 H0
      G30 P5 X-56.43 Y-155.05 Z-99999 H0
      G30 P6 X-142.89 Y-82.50 Z-99999 H0
      G30 P7 X-162.49 Y28.65 Z-99999 H0
      G30 P8 X-106.06 Y126.40 Z-99999 H0
      G30 P9 X0.00 Y82.50 Z-99999 H0
      G30 P10 X71.45 Y41.25 Z-99999 H0
      G30 P11 X71.45 Y-41.25 Z-99999 H0
      G30 P12 X0.00 Y-82.50 Z-99999 H0
      G30 P13 X-71.45 Y-41.25 Z-99999 H0
      G30 P14 X-71.45 Y41.25 Z-99999 H0
      G30 P15 X0 Y0 Z-99999 S9
      G28

      config-override.g

      ; This is a system-generated file - do not edit
      ; Delta parameters
      M665 L457.600 R266.600 H677.000 B175.0 X0.000 Y0.000 Z0.000
      M666 X0.000 Y0.000 Z0.000 A0.00 B0.00
      ; Heater model parameters
      M307 H0 A119.9 C608.9 D1.4 S1.00 V0.0 B1
      M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0
      M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
      M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
      M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
      M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
      M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0

      baird1faundefined 1 Reply Last reply Reply Quote 0
      • baird1faundefined
        baird1fa @oneearthtech
        last edited by

        @oneearthtech okay. So did everything work before you saved the config-override.g for the first time. Then after that it stopped working? Perhaps erase the data I. The config-override.g and see if things work again. That will tell you if there is something in the config-override.g that is the issue.

        Looking through your config.g it seems like some parameters are missing when setting up the probe. The M558 P4 F120 T18000 is okay but where are you telling it which pin to use? If you have recently updated your firmware that could be your issue. In the new firmware you have to define the input for the sensor. It looks like you are setup for old firmware that just assumes you are using z end stop input.

        Try using
        M558 P4 C”zstop” H5 F120 T18000.

        It could also be that you are missing the H parameter too. The Hparameter is the probe height, but without it, it should default to 5 anyway.

        oneearthtechundefined 1 Reply Last reply Reply Quote 0
        • oneearthtechundefined
          oneearthtech @baird1fa
          last edited by

          Hey @baird1fa

          Ok I will try erasing the config override info and see what happens.

          I am using very old firmware as the manufacturer of my printer has advise me not to upgrade as they will provide a firmware for me. I assume there is good reason for this.

          1 Reply Last reply Reply Quote 0
          • oneearthtechundefined
            oneearthtech
            last edited by

            @baird1fa

            Unfortunately erasing the config override files has no affect.

            adding C"zstop" made things worse.

            baird1faundefined 1 Reply Last reply Reply Quote 0
            • baird1faundefined
              baird1fa @oneearthtech
              last edited by

              @oneearthtech the C parameter is only for newer firmware so that shouldn’t be your issue.

              I guess I’m not much help. Sorry.

              1 Reply Last reply Reply Quote 0
              • oneearthtechundefined
                oneearthtech
                last edited by

                @baird1fa thanks so much for trying to help.

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

                  What firmware version? What Duet board? What probe type?

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • oneearthtechundefined
                    oneearthtech
                    last edited by

                    Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
                    Firmware Electronics: Duet Ethernet 1.02 or later
                    Firmware Version: 2.0(RTOS) (2018-06-05b3)
                    Web Interface Version: 1.21.1

                    Z-Probe
                    Type:
                    E0 Switch (4)
                    Trigger Height:
                    -0.1 mm
                    Trigger Value:
                    500

                    M122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet Ethernet 1.02 or later
                    Board ID: 08DDM-9FAM2-LW4SD-6J1F0-3SJ6T-TLZ7Z
                    Used output buffers: 3 of 20 (6 max)
                    === RTOS ===
                    Static ram: 28380
                    Dynamic ram: 95568 of which 60 recycled
                    Exception stack ram used: 396
                    Never used ram: 6668
                    Task NETWORK ready, free stack 908
                    Task HEAT blocked, free stack 1256
                    Task MAIN running, free stack 3548
                    === Platform ===
                    Last reset 00:06:34 ago, cause: power up
                    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 6632 bytes (slot 1)
                    Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
                    Error status: 0
                    Free file entries: 10
                    SD card 0 detected, interface speed: 20.0MBytes/sec
                    SD card longest block write time: 12.2ms
                    MCU temperature: min 32.8, current 35.6, max 36.1
                    Supply voltage: min 24.0, current 24.3, max 24.9, under voltage events: 0, over voltage events: 0
                    Driver 0: standstill, SG min/max not available
                    Driver 1: standstill, SG min/max 0/0
                    Driver 2: standstill, SG min/max 0/1023
                    Driver 3: standstill, SG min/max 0/1023
                    Driver 4: standstill, SG min/max 0/287
                    Date/time: 1970-01-01 00:00:00
                    Slowest loop: 76.11ms; fastest: 0.07ms
                    === Move ===
                    Hiccups: 8, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 237, MaxWait: 1680913463ms, Underruns: 0, 0
                    Scheduled moves: 121, completed moves: 121
                    Bed compensation in use: none
                    Bed probe heights: -3.242 -2.990 -3.276 -4.084 0.000
                    === Heat ===
                    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                    === GCodes ===
                    Segments left: 0
                    Stack records: 2 allocated, 0 in use
                    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
                    serial is idle in state(s) 0
                    aux is idle in state(s) 0
                    daemon is idle in state(s) 0
                    queue is idle in state(s) 0
                    autopause is idle in state(s) 0
                    Code queue is empty.
                    === Network ===
                    Slowest loop: 7.75ms; fastest: 0.01ms
                    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                    HTTP sessions: 1 of 8
                    Interface state: 5

                    oneearthtechundefined 1 Reply Last reply Reply Quote 0
                    • oneearthtechundefined
                      oneearthtech @oneearthtech
                      last edited by

                      @Phaedrux

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

                        @oneearthtech said in Z Probe Error:

                        Error: Z probe was not triggered during probing move
                        Error: Z probe already triggered at start of probing move
                        Is anyone able to help me understand what the issue might be?

                        Well if your probe is a simple switch I would start to look at the switch hardware and wiring. Has anything changed recently with it?

                        If you send a simple G30 do you get the same errors?

                        Z-Bot CoreXY Build | Thingiverse Profile

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