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

    Rostock Max V3 Z-Probe Issues

    Scheduled Pinned Locked Moved
    General Discussion
    4
    21
    840
    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.
    • Phishing Fishundefined
      Phishing Fish
      last edited by Phishing Fish

      I recently acquired a Rostock Max V3 delta printer and decided to update the firmware (was still running firmware from 2018), however, in my process of recalibrating the printer using delta calibration, my z-probe is not stopping the print head from driving into the build plate. I know the probe is functioning, as I can see the value change in the web interface when I push on the probe. I went through the process of calibrating the trigger height (got a value of -.28) however the print head is obviously not stopping there. I'm new to the duet3d system, so I'm a little unsure of what I'm doing, so this config is mostly copied from the SeeMeCNC guide for this printer. Any help is greatly appreciated!

      ; SeeMeCNC 3D Printers
      ; General preferences 
      G90                                                     ; absolute coordinates
      M83                                                     ; relative extruder moves
      
      ; Only remove ONE semi-colon for ONE M665 printer configuration
      M550 P"RostockMAX v3.2"                                 ; printer name
      ;M665 R150 L340.5 B150 H350                              ; Carbon Fiber ARMS (R delta radius, L diagonal rod length, B printable radius, H homed height default)
      M665 R142.5 L291.5 B145 H400                            ;  Standard Injection Molded Arms 
      M666 X0 Y0 Z0                                           ; endstop adjustment (this is set by autocalibration leveling)
      
      ; Network
      ;M540 P0xF0:0xE1:0xD2:0xC3:0x11:0x11	                 ; Set your own MAC Address (make different for each SeeMeCNC printer you own)
      G4 P500
      M586 P0 S1                                              ; enable HTTP
      G4 P1000
      M552 S1 P"[REDACTED]"                                                 ; enable network and acquire dynamic address via DHCP
      G4 P1000
      M586 P1 S0                                              ; disable FTP
      M586 P2 S0                                              ; disable Telnet
      M575 P1 B57600 S1                                       ; PanelDue Comm Setup
      
      ; Drives
      M569 P0 S0                                              ; physical drive 0
      M569 P1 S0                                              ; physical drive 1
      M569 P2 S0                                              ; physical drive 2
      M569 P3 S0                                              ; physical drive 3
      M569 P4 S0                                              ; physical drive 4
      M584 X0 Y1 Z2 E3:4                                      ; set drive mapping
      M350 X16 Y16 Z16 E16:16 I1                              ; configure micro stepping with interpolation
      M92 X200.00 Y200.00 Z200.00 E182.00:182.00              ; set steps per mm 
      M566 X1000.00 Y1000.00 Z1000.00 E2000.00:2000.00        ; set maximum instantaneous speed changes (mm/min)
      M203 X10000.00 Y10000.00 Z10000.00 E9000.00:9000.00     ; set maximum speeds (mm/min)
      M201 X1200.00 Y1200.00 Z1200.00 E5000.00:5000.00        ; set accelerations (mm/s^2)
      M906 X1500 Y1500 Z1500 E1400:1400 I40                   ; set motor currents (mA) and motor idle factor in per cent
      M84 S30                                                 ; Set idle timeout
      
      ; Axis Limits
      M208 Z0 S1                                              ; set minimum Z
      
      ; End-stops
      M574 X2 S1 P"xstop"                                     ; configure active-high endstop for high end on X via pin xstop
      M574 Y2 S1 P"ystop"                                     ; configure active-high endstop for high end on Y via pin ystop
      M574 Z2 S1 P"zstop"                                     ; configure active-high endstop for high end on Z via pin zstop
      
      ; Z-Probe
      M558 P5 A4 R0.4 C"zprobe.in" H50 F500 T500 B1
      G31 P50 X0 Y0 Z-0.28                                    ; set Z probe trigger value, offset and trigger height
      M557 R130 S30                                           ; define mesh grid
      
      ; Bed Heater
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin bed temp
      M950 H0 C"bedheat" T0                                   ; create bed heater output on bed heat and map it to sensor 0
      M307 H0 R0.167 K0.311:0.000 D12.22 E1.35 S1.00 B0       ; Bed Heater Process Parameters
      M140 H0                                                 ; map heated bed to heater 0
      M143 H0 S120                                            ; set temperature limit for heater 0 to 120C
      
      ; Hotend Heater
      M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8  ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1                                    ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 R3.300 C110.0115.0 D7.00 S1.00 V13.0            ; Hotend Heater Process Parameters
      M143 H1 S280                                            ; Hotend Max Temp
      
      ; Fans
      M950 F0 C"fan0" Q500                                    ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1                                          ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan2" Q500                                    ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S0.80 H1 T45                                    ; set fan 1 value. Thermostatic control is turned on
      
      ; Tool Extruder 1
      M563 P0 D0 H1 F0
      G10 P0 X0 Y0 Z0
      G10 P0 S0 R0
      
      M572 D0:1 S0.1:0.1                                      ; pressure advance for both tools
      
      ;Filament Runout Sensor
      M950 J0 C"!^e0Stop"                                     ; create switch pin
      M950 J1 C"!^e1stop"                                     ; create switch pin
      M581 P0:1 T2 S1 R1                                      ; run trigger2.g to pause if filament has run out during SD card printing
      
      ; Miscellaneous
      M575 P1 S1 B57600                                       ; enable support for PanelDue
      M501                                                    ; load saved parameters from non-volatile memory
      T0                                                      ; select Tool 0
      M911 S10.5 R11.2 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"  ; set voltage thresholds and actions to run on power loss
      M579 X1.0000 Y1.0000 Z1.0000                            ; scale axis all three must be equal
      
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by Phaedrux

        What probe is it?

        Please share your homedelta.g, and bed.g files.

        Also please send M122 and M98 P"config.g" and share the results.

        Z-Bot CoreXY Build | Thingiverse Profile

        Phishing Fishundefined 1 Reply Last reply Reply Quote 0
        • Phishing Fishundefined
          Phishing Fish @Phaedrux
          last edited by

          @Phaedrux It's an Accelorometer Probe, unsure about specifics, I cannot find anything on the SeeMeCNC website.

          Bed.g

          ; bed.g for RostockMAX v3.2
          ; updated July 2023
          ; called by G32 to perform auto calibration
          ;
          M665 R142.5 L291.5 B145 H400                ;  Standard Injection Molded Arms 
          G28                                         ; home
          M117 Heating Bed Please Wait                ; display message
          M190 S70                                    ; bed preheat temperature
          M140 S0                                     ; turn off bed
          M104 S0                                     ; hotend off
          M30 "/sys/config-override.g"                ; delete
          M30 "/sys/heightmap.csv"                    ; delete
          M561                                        ; clear any bed transform
          G30 P0 X0 Y124.42 H0 Z-99999
          G30 P1 X100.43 Y57.98 H0 Z-99999
          G30 P2 X100.43 Y-57.98 H0 Z-99999
          G30 P3 X0 Y-124.42 H0 Z-99999
          G30 P4 X-108.25 Y-62.5 H0 Z-99999
          G30 P5 X-108.25 Y62.5 H0 Z-99999
          G30 P6 X0 Y61.46 H0 Z-99999
          G30 P7 X46.77 Y-27 H0 Z-99999
          G30 P8 X-54.13 Y-31.25 H0 Z-99999
          G30 P9 X0 Y0 H0 Z-99999 S6
          M500                                        ; save
          G4 S1                                       ; pause
          M501                                        ; reload calibration 
          G4 S1                                       ; pause
          G28                                         ; home
          

          homedelta.g

          ; homedelta.g
          G91                          ; relative positioning
          G1 H1 X750 Y750 Z750 F5000   ; move all towers to the high end stopping at the end-stops (first pass)
          G1 H2 X-5 Y-5 Z-5 F5000      ; go down a few mm
          G1 H1 X10 Y10 Z10 F500       ; move all towers up once more (second pass)
          G1 Z-5 F1000                 ; move down a few mm so that the nozzle can be centered
          G90                          ; absolute positioning
          

          M112

          M122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later
          Board ID: 08DDM-9FAM2-LW4S4-6J9DJ-3SS6J-TJURZ
          Used output buffers: 3 of 26 (22 max)
          === RTOS ===
          Static ram: 23860
          Dynamic ram: 74488 of which 24 recycled
          Never used RAM 13708, free system stack 184 words
          Tasks: NETWORK(notifyWait,13.4%,237) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,86.4%,442) IDLE(ready,0.2%,30), total 100.0%
          Owned mutexes: WiFi(NETWORK)
          === Platform ===
          Last reset 00:09:38 ago, cause: power up
          Last software reset at 2023-08-22 19:55, reason: User, GCodes spinning, available RAM 13288, slot 0
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Aux0 errors 0,0,0
          Step timer max interval 0
          MCU temperature: min 22.5, current 29.6, max 30.0
          Supply voltage: min 12.3, current 12.3, max 12.5, 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-08-23 10:43:58
          Cache data hit count 4294967295
          Slowest loop: 6.78ms; fastest: 0.19ms
          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 1.0ms, 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
          Heater 1 is on, I-accum = 0.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: 13.97ms; fastest: 0.00ms
          Responder states: HTTP(0) HTTP(2) 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 2.1beta2
          WiFi MAC address 60:01:94:73:60:33
          WiFi Vcc 3.38, reset reason Turned on by main processor
          WiFi flash size 4194304, free heap 39856
          WiFi IP address 10.0.0.17
          WiFi signal strength 0dBm, mode 802.11n, reconnections 0, sleep mode modem
          Clock register 00002002
          Socket states: 0 0 0 0 0 0 0 0
          

          M98 P"config.g"

          M98 P"config.g"
          HTTP is enabled on port 80
          FTP is disabled
          TELNET is disabled
          Warning: Macro file config-override.g not found
          
          dc42undefined 1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @Phishing Fish
            last edited by

            AFAIR the probe on the Rostock 3 is similar to the Duet3D Smart Effector.

            If the probe isn't triggering when the G30 commands are executed but does trigger when you tap the nozzle upwards, it probably means that when the probe contacts the bed, the force on the nozzle doesn't increase fast enough. Possible reasons for this include:

            • Probing too slowly. You have the probing speed set to 500mm/min in the M558 command. We recommend 1200 for the Smart Effector.
            • Bed surface too soft
            • Too much give in the motion system due to e.g. loose belts.

            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

            Phishing Fishundefined 1 Reply Last reply Reply Quote 0
            • Phishing Fishundefined
              Phishing Fish @dc42
              last edited by

              @dc42 The probe triggers when running G30, but not G32. I bumped up the probing speed to 1200 however, it still is not stopping. It is a misconfiguration in my bed.g?

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

                @Phishing-Fish thanks, that's important information. Two things:

                1. Delete the M665 command in bed.g. You should have only the one in config.g, also there may be one in config-override.g if you are using that file.

                2. When you run G32, after homing does the head move rapidly to a position over the bed and then more slowly down before crashing into the bed? Or does it move and crash in a single movement? If in a single movement, then it's likely that your M665 H parameter is too high. See https://docs.duet3d.com/en/User_manual/Tuning/Delta_calibration#running-auto-calibration-for-the-first-time and the following section.

                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

                Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                • Phishing Fishundefined
                  Phishing Fish @dc42
                  last edited by

                  @dc42 I commented out the M665 command in bed.g. I don't have a config-override.g, so the one in config.g should be the only M665 command.

                  When I run G32, it runs straight down into the board, afterward I quickly cut power to the printer to avoid damaging it. I followed the directions on the link you set, with the M665 H parameter being the height of the nozzle away from the board when all three end-stops are triggered. This value was very close to 400mm when I measured, and this lines up with the default value of 400mm when I got this config from SeeMeCNC's site.

                  With the removed M665 command from bed.g and no change to the M665 H value, as I measured it at 400mm, I tested again and unfortunately still no luck. Whenever the Z-probe is triggered (anything above the value of 0 it seems) a blue light comes on. I see this light come on when the nozzle collides with the board, however, the printer does not stop.

                  Again, thank you for the continued help

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

                    @Phishing-Fish please follow the suggestion in the link I posted to increased the H (dive height) parameter in the M558 command in config.g temporarily.

                    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

                    Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                    • Phishing Fishundefined
                      Phishing Fish @dc42
                      last edited by

                      @dc42 Changed it from 400 to 300, still crashed. Changed from 300 to 200 and it did stop, about an inch away from the bed, never went down and touched it. From there drove itself into one of the vertical beams and I stopped it. I'm assuming this means my M665 H value is incorrect, however in the guide it says to measure the distance from the nozzle to the bed in mm. I get right near 400. Is there something else I should be doing?

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

                        @Phishing-Fish it looks to me that you ignored my previous reply. Also if reducing the M665 H parameter didn't help then I suspect that you still have another M665 command in one of your files.

                        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

                        Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                        • Phishing Fishundefined
                          Phishing Fish @dc42
                          last edited by

                          @dc42 Apologies for the confusion on my end. I did increase my M558 H value but forgot to mention it. I bumped it up from 5 to 30, as the guide suggested, and still didn't have any luck. I bumped it up to 50 just to see if maybe it needed more space, still crashed. As for reducing my M665 H value, I double-checked both my config.g and bed.g files and there is only one line that has M665. Is there a reason that changing the M665 H value would prevent it from hitting the board, and is there a way to determine what value it should be? Again, thank you for the continued help, it is greatly appreciated!

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

                            @Phishing-Fish you can run M665 with no parameters to see what the current value is.

                            Also check what coordinates DWC reports after homing. X and Y should be zero, and Z should be about 5mm lower than the current M665 H parameter, if you are using our standard homedelta.g file.

                            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

                            Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                            • Phishing Fishundefined
                              Phishing Fish @dc42
                              last edited by

                              @dc42 M665 results: Diagonals 291.500:291.500:291.500, delta radius 142.500, homed height 200.000, bed radius 145.0, X 0.000°, Y 0.000°, Z 0.000°.

                              After homing, DWC reports X and Y at zero, Z at 195. I would make my M665 H value 190 then, and see if it stops before crashing? Also, I'm unsure if I'm using the stand homedelta.g file, so I've attached it here.

                              ; homedelta.g
                              G91                          ; relative positioning
                              G1 H1 X750 Y750 Z750 F5000   ; move all towers to the high end stopping at the end-stops (first pass)
                              G1 H2 X-5 Y-5 Z-5 F5000      ; go down a few mm
                              G1 H1 X10 Y10 Z10 F500       ; move all towers up once more (second pass)
                              G1 Z-5 F1000                 ; move down a few mm so that the nozzle can be centered
                              G90                          ; absolute positioning
                              
                              dc42undefined 1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators @Phishing Fish
                                last edited by dc42

                                @Phishing-Fish are you certain that you have the correct steps/mm set? For example, if you home the printer and then command Z to reduce by 25mm, does the effector drop 25mm?

                                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

                                Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                                • Phishing Fishundefined
                                  Phishing Fish @dc42
                                  last edited by

                                  @dc42 This looks like a potential issue. I brought the nozzle down to the bed and pressed the Z+25 button. Measuring it, it looks like it went up nearly 65mm. How do I go about corrected/calibrating this?

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

                                    @Phishing-Fish said in Rostock Max V3 Z-Probe Issues:

                                    How do I go about corrected/calibrating this?

                                    That's a pretty substantial difference. What are the motors you're using? 1.8 or 0.9 degree? Belt pitch? Idler tooth count? Microstepping?

                                    Z-Bot CoreXY Build | Thingiverse Profile

                                    Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                                    • Phishing Fishundefined
                                      Phishing Fish @Phaedrux
                                      last edited by

                                      @Phaedrux Motors are Automation Technology KL17H248-15-4A. Looking at what I can find online, I couldn't find anything related to 1.8 or 0.9 degree, but I did find a step angle of 1.8° ± 5%. For belt pitch, it's 2mm. Belts can be found here: https://www.seemecnc.com/products/gt2-timing-belt. Looking at the build guide for this printer, it seems like the idlers do not have teeth and looking at my printer don't see any. For micro stepping, this is what I have in my config.g: M350 X16 Y16 Z16 E16:16 I1

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

                                        @Phishing-Fish your M92 command shows 200 steps/mm. With x16 microstepping, that would be correct if the motors are 0.9 degrees and the motor pulleys have 16 teeth. If the motors are 1.8deg then it would be 100 steps/mm with 16 tooth pulleys, or 80 steps/mm with 20 tooth pulleys.

                                        If the correct steps/mm for your machine is actually 80 instead of 200, that would cause a commanded 25mm movement to move 62.5mm.

                                        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

                                        Phishing Fishundefined 1 Reply Last reply Reply Quote 0
                                        • A Former User?
                                          A Former User
                                          last edited by

                                          This post is deleted!
                                          1 Reply Last reply Reply Quote 1
                                          • Phishing Fishundefined
                                            Phishing Fish @dc42
                                            last edited by

                                            @dc42 That worked! Changing the steps/mm to 80 in config.g and now the auto-calibration stops when it hits the board. Thinking back on it now, I should have known the motors were running faster than they should have, but it never crossed my mind. To confirm, I should run the auto-calibration, then M500 to save the results in override-config.g, and then put M501 at the end of config.g, so that override-config.g is used?

                                            Thank you both so much for the continued help!

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