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

    Many issues after upgrading to 3.0 RC-12

    Scheduled Pinned Locked Moved
    Firmware installation
    6
    34
    1.8k
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      Make sure your probe offset is correct. -X to the left, +X to the right. -Y to the front, +Y to the back.

      https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Measuring_Probe_X_Y_Offset

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • TheBasedDogeundefined
        TheBasedDoge
        last edited by

        Ah ok, that was wrong. my probe is front right of the primary nozzle, so i changed it now to read y-5

        Still having the same issue, back third of the bed will not probe

        G29
        Warning: Skipping grid point (20.0, 215.0) because Z probe cannot reach it
        Warning: Skipping grid point (70.0, 215.0) because Z probe cannot reach it
        Warning: Skipping grid point (120.0, 215.0) because Z probe cannot reach it
        Warning: Skipping grid point (170.0, 215.0) because Z probe cannot reach it
        Warning: Skipping grid point (220.0, 215.0) because Z probe cannot reach it
        Warning: Skipping grid point (270.0, 215.0) because Z probe cannot reach it
        Warning: Skipping grid point (270.0, 265.0) because Z probe cannot reach it
        Warning: Skipping grid point (220.0, 265.0) because Z probe cannot reach it
        Warning: Skipping grid point (170.0, 265.0) because Z probe cannot reach it
        Warning: Skipping grid point (120.0, 265.0) because Z probe cannot reach it
        Warning: Skipping grid point (70.0, 265.0) because Z probe cannot reach it
        Warning: Skipping grid point (20.0, 265.0) because Z probe cannot reach it

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

          Please post your whole config.g file as it is now.

          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
          • TheBasedDogeundefined
            TheBasedDoge
            last edited by

            Ok, here it is. thank you!

            ; Configuration file for Duet WiFi (firmware version 3)
            ; executed by the firmware on start-up
            ;
            ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun May 10 2020 13:55:08 GMT-0400 (Eastern Daylight Time)
            
            ; General preferences
            G90                                                    ; send absolute coordinates...
            M83                                                    ; ...but relative extruder moves
            M550 P"Hypercube"                                      ; set printer name
            
            M667 S1                                                ; select CoreXY mode
            
            ; Network
            M552 S1                                                ; enable network
            M586 P0 S1                                             ; enable HTTP
            M586 P1 S0                                             ; disable FTP
            M586 P2 S0                                             ; disable Telnet
            
            ; Drives
            M569 P0 S1                                             ; physical drive 0 goes forwards
            M569 P1 S1                                             ; physical drive 1 goes forwards
            M569 P2 S1                                             ; physical drive 2 goes forwards
            M569 P3 S1                                             ; physical drive 3 goes forwards
            M569 P4 S1                                             ; physical drive 4 goes forwards
            M584 X0 Y1 Z2 E3:4                                     ; set drive mapping
            M350 X16 Y16 Z16 E16:16 I1                             ; configure microstepping with interpolation
            M92 X80.00 Y80.00 Z400.00 E86.00:86.00                 ; set steps per mm
            M566 X900.00 Y900.00 Z12.00 E120.00:120.00             ; set maximum instantaneous speed changes (mm/min)
            M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00        ; set maximum speeds (mm/min)
            M201 X5000.00 Y5000.00 Z20.00 E250.00:250.00             ; set accelerations (mm/s^2)
            M906 X800 Y800 Z800 E800:800 I30                       ; set motor currents (mA) and motor idle factor in per cent
            M84 S30                                                ; Set idle timeout
            
            ; Axis Limits
            M208 X0 Y0 Z0 S1                                       ; set axis minima
            M208 X300 Y0 Z0 S0                                     ; set axis maxima
            
            ; Endstops
            M574 X1 S1 P"!xstop"                                    ; configure active-low endstop for low end on X via pin xstop
            M574 Y1 S1 P"!ystop"                                    ; configure active-low endstop for low end on Y via pin ystop
            M574 Z1 S2                                              ; configure Z-probe endstop for low end on Z
            
            ; Z-Probe
            M950 S0 C"exp.heater7"                                 ; create servo pin 0 for BLTouch
            M558 P9 C"^zprobe.in" H5 F120 T6000   A5 S0.02         ; set Z probe type to bltouch and the dive height
            G31 P500 X20 Y-5 Z3.7                                   ; set Z probe trigger value, offset and trigger height
            M557 X20:290 Y0:290 S50                               ; define mesh grid
             
            
            ; Heaters
            M308 S0 P"bedtemp" Y"thermistor" T100000 B4138         ; configure sensor 0 as thermistor on pin bedtemp
            M950 H0 C"bedheat" T0                                  ; create bed heater output on bedheat and map it to sensor 0
            M143 H0 S120                                           ; set temperature limit for heater 0 to 120C
            M307 H0 B1 S1.00                                       ; enable bang-bang mode for the bed heater and set PWM limit
            M140 H0                                                ; map heated bed to heater 0
            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
            M143 H1 S280                                           ; set temperature limit for heater 1 to 280C
            M307 H1 B0 S1.00                                       ; disable bang-bang mode for heater  and set PWM limit
            M308 S2 P"e1temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin e1temp
            M950 H2 C"e1heat" T2                                   ; create nozzle heater output on e1heat and map it to sensor 2
            M143 H2 S280                                           ; set temperature limit for heater 2 to 280C
            M307 H2 B0 S1.00                                       ; disable bang-bang mode for heater  and set PWM limit
            
            ; 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"fan1" Q500                                   ; create fan 1 on pin fan1 and set its frequency
            M106 P1 S1 H1:2 T100                                   ; set fan 1 value. Thermostatic control is turned on
            M950 F2 C"fan2"					       ; Board cooling fan
            M106 P2 S80 H-1
            
            ; Tools
            M563 P0 S"Right Nozzle" D0 H1 F0                       ; define tool 0
            G10 P0 X0 Y0 Z0                                        ; set tool 0 axis offsets
            G10 P0 R0 S0                                           ; set initial tool 0 active and standby temperatures to 0C
            M563 P1 S"Left Nozzle" D1 H2 F0                        ; define tool 1
            G10 P1 X0 Y0 Z0                                        ; set tool 1 axis offsets
            G10 P1 R0 S0                                           ; set initial tool 1 active and standby temperatures to 0C
            
            ; Custom settings
            M575 P1 B57600 S1                                      ;paneldue settings to enable connection
            M564 H0                                                ;allow movement before homing
            M501 						       ;load config overrides
            
            
            
            sebkritikelundefined 1 Reply Last reply Reply Quote 0
            • sebkritikelundefined
              sebkritikel @TheBasedDoge
              last edited by

              @TheBasedDoge said in Many issues after upgrading to 3.0 RC-12:

              Ok, here it is. thank you!

              ; Configuration file for Duet WiFi (firmware version 3)
              ; executed by the firmware on start-up
              ;
              ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun May 10 2020 13:55:08 GMT-0400 (Eastern Daylight Time)
              ; Axis Limits
              M208 X0 Y0 Z0 S1                                       ; set axis minima
              M208 X300 Y0 Z0 S0                                     ; set axis maxima
              

              M208 X300 Y0 Z0 S0 ; set axis maxima

              That looks like a mistake - Y300 right??

              Large(ish?) IDEX - 6HC, 1HCL
              Stratasys Dimension 1200es to 6HC Conversion

              TheBasedDogeundefined 1 Reply Last reply Reply Quote 3
              • TheBasedDogeundefined
                TheBasedDoge @sebkritikel
                last edited by

                @sebkritikel

                Yeah that seems to have been it. I was using the RR config tool and I don't think it filled in any of this stuff correctly. I set my maxima for XYZ now correctly and ran the probing again and it seems to have worked.

                One more thing - on my RR 2 FW the BLTouch only probed each spot 1 time, now it does it like 4 times. Is this a setting somewhere?

                Also wondering on the correct way to do start Gcode with mesh enabled. I have this:

                G29 S1 ;Load heatmap
                G28
                
                G1 Z15.0 F7000 ;Move the platform down 15mm
                G92 E0
                G1 F200 E3
                G92 E0
                
                G1 X150 Y150 F7000 ; Move Probe to middle of bed
                G30 ; Do a single probe
                

                Should I change anything?

                dc42undefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
                • dc42undefined
                  dc42 administrators @TheBasedDoge
                  last edited by

                  @TheBasedDoge said in Many issues after upgrading to 3.0 RC-12:

                  One more thing - on my RR 2 FW the BLTouch only probed each spot 1 time, now it does it like 4 times. Is this a setting somewhere?

                  Yes, see the documentation for M558.

                  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
                  • TheBasedDogeundefined
                    TheBasedDoge
                    last edited by

                    Got it - I just noticed this error after starting a print

                    Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.

                    I am watching the Z motor and it seems to be adjusting as the head moves around though.

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

                      @TheBasedDoge said in Many issues after upgrading to 3.0 RC-12:

                      Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.

                      https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation#Section_Establish_a_Z_0_datum_using_the_Z_probe

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • TheBasedDogeundefined
                        TheBasedDoge
                        last edited by

                        So I read this and I am still a little confused why it's happening - because I did this:
                        "Move the nozzle over the centre of the bed and do a single G30 probe (G30 without parameters)."
                        The center of bed G30 is in my start gcode for each print.

                        The only difference that I did not do is run the G29 while the printer was hot. Is this the reason the error is coming up?

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

                          @TheBasedDoge said in Many issues after upgrading to 3.0 RC-12:

                                                                                                                                                      G29 S1 ;Load heatmap                                                                                                                                                                            G28                                                                                                                                                                                                                                                                                                                                                         G1 Z15.0 F7000 ;Move the platform down 15mm                                                                                                                                                                            G92 E0                                                                                                                                                                            G1 F200 E3                                                                                                                                                                            G92 E0                                                                                                                                                                                                                                                                                                                                                         G1 X150 Y150 F7000 ; Move Probe to middle of bed                                                                                                                                                                            G30 ; Do a single probe
                          

                          You've loaded the heightmap before you've done the G30. That's the problem.

                          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