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

    smart effector g32 issues

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    17
    575
    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.
    • sankafolaundefined
      sankafola
      last edited by

      hello,
      i have Duet 3 SBC setup and i installed smart effector , i do the the G30 the nozzle goes down and touch the bed and go up and works fine , when i start auto calibration in my delta Anycubic , the nozzle crash on the bed and drag the nozzle ,

      my M665 R227 L440.43 B185 H404.22
      please help

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        post your entire config and config overwrite

        1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @sankafola
          last edited by

          @sankafola I would increase the dive height in your first probe. That's the 'H' value in M558. Use something like 30

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          sankafolaundefined 1 Reply Last reply Reply Quote 1
          • sankafolaundefined
            sankafola @jay_s_uk
            last edited by

            @jay_s_uk thanks that worked

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

              Once you have corrected your M665 and M666 values following auto calibration, you can reset the dive height to a lower value such as 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

              sankafolaundefined 1 Reply Last reply Reply Quote 0
              • sankafolaundefined
                sankafola @dc42
                last edited by

                @dc42 can you please help , i have SKR 1.4 turbo and i installed the Rerap 3 on it with SBC raspberry pi , and smart effector and magballs , i have connected the wires to the servo GND power 5v , and the output Z , the smart effector do the 2 flashes and do the probing and all is fine except when i print i have to do baby step + 0.8 , what am doing wrong do i need to put the mod pin and if yes where ? and how do i fix this babastep + 0.80 for good ?

                1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk
                  last edited by

                  @dc42 just to verify, currently he has the mod pin not connected.
                  When setting the probe so its G31 settings are G31 P100 X0 Y0 Z-0.1, as is typical for the smart effector, 0.8mm of baby stepping is required to obtain a first layer.
                  If the G31 is modified to G31 P100 X0 Y0 Z-0.75, 0.8mm of baby stepping is still required to obtain a first layer.

                  any thoughts?

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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

                    The Smart Effector mod pin can be left disconnected if the default sensitivity is working.

                    Z-0.75 is not usual, unless the bed or the delta mechanics are very soft. I suspect that either auto calibration has not been run, or the results from it have not been saved, or they have been saved in config-override.g but there is no M501 command in config-override.g.

                    What are the M558 parameters, in particular the probing speed?

                    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

                    sankafolaundefined 3 Replies Last reply Reply Quote 0
                    • sankafolaundefined
                      sankafola @dc42
                      last edited by

                      @dc42 i ran the auto calibrate , the M501 is in the config and uncommented and my M558 is

                      M558 P8 H2 F1000 T12000 R0.2 S0.02 A5 C"servo0"

                      1 Reply Last reply Reply Quote 0
                      • sankafolaundefined
                        sankafola @dc42
                        last edited by

                        @dc42 that is my config file

                        ; Configuration file for SKR v1.4 (firmware version 3)
                        ; executed by the firmware on start-up
                        ;
                        ; generated by RepRapFirmware Configuration Tool v3.1.3-LPC-1 on Sat Aug 22 2020 07:45:45 GMT-0400 (Eastern Daylight Time)

                        ; General preferences

                        M564 S0 H0
                        G90 ; send absolute coordinates...
                        M83 ; ...but relative extruder moves
                        M550 P"Duet 3" ; set printer name
                        M665 R221.139 L440.43 B184.9 H400.752 ; Set delta radius, diagonal rod length, printable radius and homed height
                        M666 X-0.054 Y0.510 Z-0.456 ; put your endstop adjustments here, or let auto calibration find them

                        ; Drives
                        M569 P0 S0 ; physical drive 0 goes backwards using default driver timings
                        M569 P1 S0 ; physical drive 1 goes backwards using default driver timings
                        M569 P2 S0 ; physical drive 2 goes backwards using default driver timings
                        M569 P3 S1 ; physical drive 3 goes forwards using default driver timings
                        M584 X0 Y1 Z2 E3 ; set drive mapping
                        M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
                        M92 X80.00 Y80.00 Z80.00 E435.00 ; set steps per mm BMG 415
                        M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
                        M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
                        M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
                        M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
                        M84 S30 ; Set idle timeout

                        ; Axis Limits
                        ;M208 Z-3 S1 ; set minimum Z

                        ; Endstops
                        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 P8 C"e1stop"H5 F600 T6000 ; set Z probe type to switch and the dive height + speeds
                        ;G31 P500 X7 Y7 Z17.80 ; set Z probe trigger value, offset and trigger height
                        ;M557 R85 S20 ; define mesh grid

                        G31 P100 X0 Y0 Z0.1
                        M558 P8 H2 F1000 T12000 R0.2 S0.02 A5 C"servo0"
                        ;M558 P8 H4 F1000 T12000 R0.2 S0.02 A5 C"servo0+!probe"
                        ;M558 P8 C"!e1stop"H5 F600 T6000 ; set Z probe type to switch and the dive height + speeds

                        ; Heaters2
                        M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
                        M950 H0 C"bed" T0 ; create bed heater output (2.5) on bed and map it to sensor 0
                        M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
                        M140 H0 ; map heated bed to heater 0
                        M143 H0 S120 ; set temperature limit for heater 0 to 120C
                        M308 S1 P"e0temp" Y"pt1000" R4700 ; configure sensor 1 as PT1000 on pin e0temp
                        M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
                        M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
                        M143 H1 S420 ; set temperature limit for heater 1 to 420C
                        ; Heater model parameters
                        ;M307 H0 A150.1 C573.4 D0.5 S1.00 V0.0 B0
                        ;M307 H1 A521.9 C138.6 D6.8 S1.00 V0.0 B0

                        ; Fans
                        ;M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 (2.3) and set its PWM frequency
                        ;M106 P0 S0 H-1 C"Parts Cooling" ; set fan 0 (P0) value to off. Thermostatic control is turned off (H-1)
                        ;M950 F1 C"e1heat" T1 ; create extruder fan output (2.4) on e1heat and map it to sensor 1 (T1)
                        ;M106 P1 R1 H1 T45 C"Hotend Cooling" ; thermostatically 45C controlled fan from T1 sensor

                        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"e1heat" Q500 ; Create fan 1 on pin fan1 and set its frequency
                        M106 P1 S1 H1 T45 ; Set fan 1 value. Thermostatic control is turned on

                        ; Tools
                        M563 P0 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

                        ; Automatic saving after power loss
                        ;M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"

                        ; Miscellaneous
                        M575 P1 S3 B57600 ; enable support for PanelDue a.k.a TFT35 V3.0

                        ; Uncomment M501 to load EEPROM file - config-override.g
                        M501 ; load saved parameters from config-override.g

                        T0 ; select T0 as active tool
                        ;G28 ; home the printer
                        G4 ; Wait for moves to finish
                        ;G28 ; to be sure, to be sure

                        ;M591 D0 P1 ;Run out sensor
                        M591 D0 P2 C"e0stop" S1 ; filament monitor connected to E0 endstop

                        Vetiundefined 1 Reply Last reply Reply Quote 0
                        • Vetiundefined
                          Veti @sankafola
                          last edited by

                          @sankafola said in smart effector g32 issues:

                          G31 P100 X0 Y0 Z0.1
                          M558 P8 H2 F1000 T12000 R0.2 S0.02 A5 C"servo0"

                          see https://duet3d.dozuki.com/Wiki/Gcode#Section_G31_Set_or_Report_Current_Probe_status

                          A G31 command to set Z probe parameters must come after the M558 command that defines the Z probe.

                          @sankafola said in smart effector g32 issues:

                          M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp

                          4138 is the default and wrong for your thermistor

                          sankafolaundefined 1 Reply Last reply Reply Quote 0
                          • sankafolaundefined
                            sankafola @Veti
                            last edited by sankafola

                            @Veti i have PT1000 thiermster what would be the value because am getting a lot of heater fault too what is the bed value and the hotend please ?/>

                            Vetiundefined 1 Reply Last reply Reply Quote 0
                            • Vetiundefined
                              Veti @sankafola
                              last edited by

                              @sankafola

                              you have a pt1000 on your hotend, but your bed has a thermistor. which thermistor you have i can not tell you. you will have to look that up from the sales information.

                              sankafolaundefined 1 Reply Last reply Reply Quote 0
                              • sankafolaundefined
                                sankafola @Veti
                                last edited by

                                @Veti found it M308 S0 P"bedtemp" Y"thermistor" T100000 B4300 C0 R4700

                                1 Reply Last reply Reply Quote 0
                                • sankafolaundefined
                                  sankafola @dc42
                                  last edited by

                                  @dc42 the bed have the whambam with PEX maybe that is why ? what do i need to do ?

                                  1 Reply Last reply Reply Quote 0
                                  • jay_s_ukundefined
                                    jay_s_uk
                                    last edited by

                                    My machine has whambam PEX and I use the default 0.1 perfectly

                                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                    sankafolaundefined 1 Reply Last reply Reply Quote 1
                                    • sankafolaundefined
                                      sankafola @jay_s_uk
                                      last edited by

                                      @jay_s_uk all good now did the procedure again for delta calibration and now seem fine thanks all for the help

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