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

    Tevo Little Monster calibration issues with RRF 3.1.1

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    8
    539
    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.
    • Sytac072undefined
      Sytac072
      last edited by

      Hi everyone. I own a Tevo Little Monster which I have upgraded with Duet2 WiFi, magnetic rods and Smart Effector.
      I have used the printer for a long time with RRF firmware until the latest one which was 2.05.1 and the printer works perfectly, without any trouble. Then I tried to upgrade to RRF 3.1.1 (doing the needed changes to the config files).
      At this point, I started to have troubles with the Z offset, which was always to be calibrated at every startup of the printer, as well as the mesh calibration, which is not working.
      Even during the printing process, it's difficult to have a good result, then I have reinstalled the previous one (2.05.1) and everything went back to normal.
      Anyone has any idea?

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

        post your config and overwrite

        Sytac072undefined 1 Reply Last reply Reply Quote 0
        • Sytac072undefined
          Sytac072
          last edited by

          ; Configuration file for Duet WiFi (firmware version 3)
          ; executed by the firmware on start-up
          ;
          ; generated by RepRapFirmware Configuration Tool v2.1.4 on Mon Jan 06 2020 13:06:19 GMT+0100 (Ora standard dell’Europa centrale)

          ; General preferences
          G28 ; Home all axes
          M111 S0 ; Debugging off
          G21 ; Works in millimiters
          G90 ; send absolute coordinates...
          M83 ; ...but relative extruder moves
          M555 P1 ; Set firmware compatibility to look like RepRap Firmware
          M665 L400.25:400.25:400.25 R165 B160 H485 ; Set delta radius, diagonal rod length, printable radius and homed height (With extra glass 13/07/2020)
          M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
          M575 P1 B57600 S1 ; set paneldue communication parameters

          ; Network

          M550 P"TEVO Little Monster" ; Set machine name
          M552 S1 ; Enable network

          M586 P0 S1 ; Enable HTTP
          M586 P1 S1 ; Enable FTP
          M586 P2 S0 ; Disable Telnet

          ; Drives
          M569 P0 S0 ; physical drive 0 goes backwards
          M569 P1 S0 ; physical drive 1 goes backwards
          M569 P2 S0 ; physical drive 2 goes backwards
          M569 P3 S0 ; physical drive 3 goes backwards
          M584 X0 Y1 Z2 E3 ; set drive mapping
          M579 X1.00806 Y1.007252 Z1.0040 ; Scale parameter for axes X, Y and Z calculated on 16/05/2020
          M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
          M92 X160.00 Y160.00 Z160.00 E819.338 ; set steps per mm
          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 X1250 Y1250 Z1250 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent
          M84 S30 ; Set idle timeout

          ; Axis Limits
          M208 Z0 S1 ; set minimum Z

          ; Endstops
          M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
          M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
          M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop

          ; Z-Probe
          M558 P8 R0.8 C"zprobe.in+zprobe.mod" H5 A5 F1200 T6000 ; set Z probe type to effector and the dive height + speeds (New setting from 15/05/2020)
          ;M558 P5 R0.4 C"zprobe.in+zprobe.mod" H1 F1200 T6000 ; set Z probe type to effector and the dive height + speeds (New setting from 10/01/2020)
          ;M558 P5 R0.4 C"zprobe.in+zprobe.mod" H5 F1200 T6000 ; set Z probe type to effector and the dive height + speeds (Original setting)
          G31 P500 X0 Y0 Z-0.152 ; set Z probe trigger value, offset and trigger height
          M557 R150 S15 ; define mesh grid (New setting from the old config.g)
          ;M557 R85 S15 ; define mesh grid (Original setting from configurator)

          ; Heaters
          ; Reference page : https://duet3d.dozuki.com/Wiki/Connecting_thermistors_or_PT1000_temperature_sensors
          M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700 A"Piatto" ; 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
          M140 H0 ; define and create the bed heater (set on 13/05/2020, needed with RRF 3)
          M143 H0 S120 ; set temperature limit for heater 0 to 120C
          M307 H0 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit
          M308 S1 P"e0temp" Y"thermistor" T100000 B4725 R4375 C7.06e-8 A"Estrusore"; 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 the nozzle heater and set PWM limit

          ; Fans
          M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
          M106 P0 C"Part cooling fan" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
          M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
          M106 P1 C"Hotend fan" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on

          ; Tools
          M563 P0 D0 H1 F-1 ; 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

          ; Filament run-out sensor
          M591 D0 P2 C3 S1 ; Filament run-out sensor Input high when filament is in

          ; Automatic power saving
          M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

          ; Miscellaneus
          M375 ; Load the grid probing mesh
          M501 ; read stored parameters from config override

          Phaedruxundefined 1 Reply Last reply Reply Quote 0
          • Sytac072undefined
            Sytac072 @Veti
            last edited by

            @Veti
            ; config-override.g file generated in response to M500 at 2020-09-17 13:01
            ; This is a system-generated file - do not edit
            ; Delta parameters
            M665 L407.671:407.671:407.671 R167.529 H473.244 B160.0 X-0.109 Y-0.362 Z0.000
            M666 X1.320 Y0.069 Z-1.390 A0.07 B-0.19
            ; Heater model parameters
            M307 H0 A171.3 C936.8 D0.9 S1.00 V23.9 B0
            M307 H1 A294.8 C253.4 D3.1 S1.00 V23.7 B0
            ; Workplace coordinates
            G10 L2 P1 X0.00 Y0.00 Z0.00
            G10 L2 P2 X0.00 Y0.00 Z0.00
            G10 L2 P3 X0.00 Y0.00 Z0.00
            G10 L2 P4 X0.00 Y0.00 Z0.00
            G10 L2 P5 X0.00 Y0.00 Z0.00
            G10 L2 P6 X0.00 Y0.00 Z0.00
            G10 L2 P7 X0.00 Y0.00 Z0.00
            G10 L2 P8 X0.00 Y0.00 Z0.00
            G10 L2 P9 X0.00 Y0.00 Z0.00

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

              my first question would be why your endstops are set to the low end of the printer?
              surely being a delta you home with the carriages being at the top of the frame?

              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

              Sytac072undefined 1 Reply Last reply Reply Quote 0
              • Sytac072undefined
                Sytac072 @jay_s_uk
                last edited by

                @jay_s_uk

                Yes, you are right. This is already a mistake but the homing process works correctly anyway.

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

                  I would also suggest looking at your trigger value. you have P500 but the recommended value for the smart effector is P100
                  https://duet3d.dozuki.com/Wiki/Smart_effector_and_carriage_adapters_for_delta_printer#Section_Commissioning

                  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
                  • Phaedruxundefined
                    Phaedrux Moderator @Sytac072
                    last edited by

                    @Sytac072 said in Tevo Little Monster calibration issues with RRF 3.1.1:

                    G28 ; Home all axes

                    You probably should not initiate a homeall in your config.g. For one thing, you have it at the start of the config.g before any of the configuration has loaded. Second, having movement start with power on is potentially dangerous.

                    Did you change the endstops to be at high end?

                    @Sytac072 said in Tevo Little Monster calibration issues with RRF 3.1.1:

                    M375 ; Load the grid probing mesh

                    Also, you should not load the heightmap until after the printer has been homed and the bed probed to establish Z0. This is likely part of the problem with your inconsistent offset.

                    Are you using G32/bed.g to do a calibration? It should be in your bed.g macro that you home the towers and probe the bed for calibration and only then do a G29 to create or load a heightmap.

                    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