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

    Touch Probe troubleshooting

    Scheduled Pinned Locked Moved
    CNC
    1
    4
    268
    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.
    • xavierbundefined
      xavierb
      last edited by

      I'm very stumped right now.

      I have a hybrid cnc and 3d printer, I have a mesh bed macro to allow me to probe my cnc parts for when I go to 3D print directly onto the cnc'ed part.

      I have taken 4 week break after cramming nonstop for 5 months and I forgot about some of the alterations I made to firmware to get it working. My touch probe in particular has been acting up. After setting my Z the probe, it was actually reporting 24.00mm too high. I then found out in my override file that I had a override of 24.20mm. After rectifying that issue, I then went back to probe and my bit crashed while probing.

      I haven't touched anything else in my code aside a G10 Z0(which I removed), and my probe is triggering outside the probing(0-1000). Just for diagnosing sake I set the M558 F80 to MFF8 F10 and it hasn't made any noticeable difference in speed(still seams to be moving at F80).

      It feels as if I'm experiencing some sort of bug where my old settings have been overridden in some capacity. I'm completely lost.

      Any help would help would be hugely appreciated

      ; Configuration file for Duet 3 (firmware version 3.3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Jun 14 2022 16:23:32 GMT-0700 (Pacific Daylight Time)

      ; General preferences
      M575 P1 S1 B57600 ; enable support for PanelDue
      G90 ; send absolute coordinates...
      M82 ; ...but relative extruder moves
      M550 P"Onefinity Printer" ; set printer name
      G4 S1 ;wait for expansion boards to start

      ; Network
      M551 P"3dprinter" ; set password
      M552 P192.168.50.201 S1 ; enable network and acquire dynamic address via DHCP
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P0.0 S1 ; physical drive 0.0 goes forwards
      M569 P0.1 S1
      M569 P0.2 S1 ; physical drive 0.1 goes forwards
      M569 P0.3 S0 ; physical drive 0.3 goes forwards
      M569 P0.4 S1
      M569 P0.5 S0
      ;M584 X0.0 Y0.1 Z0.3 E0.4 ; set drive mapping
      M584 U0.2 X0.0 Y0.1:0.2 Z0.3 E0.4:0.5
      M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
      M92 X200.00 Y320.00 U320.00 Z800.00 E415.00:136.30 ; set steps per mm
      M566 X500.00 Y500.00 U500.00 Z600.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X3500.00 Y3500.00 U3500.00 Z2800.00 ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 U500.00 Z600.00 ; set accelerations (mm/s^2)
      M906 X2800 Y2800 Z2800 U2800 E950:950 I50 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 U0 S1 ; set axis minima
      M208 X1223 Y816 Z133 U816 S0 ; set axis maxima

      ; Endstops
      M574 X1 S3 ; configure sensorless endstop for low end on
      M574 Y1 S3 ; configure sensorless endstop for low end on

      M574 U1 S3
      M574 Z2 S3

      M915 Y R0 S-4 F1 R0 H800

      M915 U R0 S-4 F1 R0 H800

      M915 X R0 S-1 F1 R0 H400

      M915 Z R0 S-2 F1 R0 H800

      ; Z-Probe
      ;M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
      ;M557 X0:0 Y0:0 S20 ; define mesh grid
      M558 P5 C"!io1.in" H5 F10 T100
      G31 Z14.75

      ; Heaters
      M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin temp0
      M950 H1 C"out1" T0 ; create nozzle heater output on out1 and map it to sensor 0
      M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
      M143 H1 S280 A2 ; set temperature limit for heater 0 to 250C

      ; Fans
      M950 F0 C"out9" Q250 ; create fan 0 on pin out9 and set its frequency
      M950 F1 C"out8" Q250
      M950 F2 C"out7" Q250
      //m950 f1 c"out8" Q250
      //M106 S.8
      M106 P0 S.8 T45 H0 ; set fan 0 value. Thermostatic control is turned on
      M106 P1 X.8
      M106 P2 X.8

      ; Tools

      M563 H1 P0 S"Hotend" F1:2 D0:1 //F0 ; define tool 0 3Dprinter
      M563 P1 S"Spindle" //F0 ;define tool 0 CNC
      G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
      G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
      M567 P0 E1.0:1.0
      M563 P1

      ; Custom settings are not defined

      ; Accelerometer

      M955 P121.0 I20

      ; misc

      M206 Z-5.5 ; home offset raise z

      ; Miscellaneous
      T0 ; select first tool
      M501 ; load saved parameters from non-volatile memory

      Macro

      G31 Z14.75
      G30 S-2
      G1 Z20 F500

      xavierbundefined 1 Reply Last reply Reply Quote 0
      • xavierbundefined
        xavierb
        last edited by

        It was an issue with old override settings. Issue now is I've cleared the override file and now it seams like my machine is going phantom on me. I had the z offset set at 0.00, 5.50 and 24.2; it seams like it'll randomly swap between the 3 settings. As someone whos running a cnc, I'm getting extremely anxious as I have a huge project coming up.

        I can't seam to come across anyone experiencing lagging settings on their duet

        xavierbundefined 1 Reply Last reply Reply Quote 0
        • xavierbundefined
          xavierb @xavierb
          last edited by xavierb

          @xavierb So I had M206 Z-5.5 which I commented out. however after sending a M500 it still comes back.

          this is what my config overrride shoud look like

          ; config-override.g file generated in response to M500 at 2023-05-05 16:10
          ; This is a system-generated file - do not edit
          ; Heater model parameters
          M307 H1 R1.393 K0.180:0.000 D12.91 E1.35 S1.00 B0 V25.4
          M301 H1 P19.5 I1.590 D59.4
          ; Workplace coordinates
          G10 L2 P1 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P2 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P3 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P4 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P5 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P6 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P7 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P8 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P9 X0.00 Y0.00 Z0.00 U0.00

          but it looks like this after the m500

          ; config-override.g file generated in response to M500 at 2023-06-25 16:39
          ; This is a system-generated file - do not edit
          ; Heater model parameters
          M307 H1 R2.430 K0.560:0.000 D5.50 E1.35 S1.00 B0 V0.0
          ; Workplace coordinates
          G10 L2 P1 X0.00 Y0.00 Z5.50 U0.00
          G10 L2 P2 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P3 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P4 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P5 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P6 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P7 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P8 X0.00 Y0.00 Z0.00 U0.00
          G10 L2 P9 X0.00 Y0.00 Z0.00 U0.00

          1 Reply Last reply Reply Quote 0
          • xavierbundefined
            xavierb @xavierb
            last edited by xavierb

            @xavierb

            I removed the M501 at the end of my config and deleted my config override. I'm a bit sketched out that this might have some unforeseen consequence, but this will have to due for the moment

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