Delta Printer calibration issue

  • I am having an issue and I don't really know how to describe it or where to start to fix it, when I put the print head to 0 on the x, y and z axis the hotend is in the correct position and correct distance from the bed, however if I move the print head in the x or y direction it seems to lift in the z axis. Any idea what may be causing it? I am thinking it may be my belt tension however they aren't too tight or too slack, could it be an error in the firmware?config (1).g


    Here is a quick video to better explain what I'm trying to describe

  • config (2).json

    This is my config file.

  • Moderator

    Post your config.g instead of config.json.
    Post your bed.g as well.

    What kind of a delta is it?

    I suggest you go through this guide as a start.

  • @Phaedrux config (2).g bed.g

    The kind of delta would be custom I guess?

  • Moderator

    Thanks, hopefully that info will help a delta savvy user give you some ideas.

    Firmware version? From the config it looks like RRF3 at least. Should be 3.1.1 if not already. Check with M115 to be sure.

  • @Phaedrux FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2020-05-19b2

  • @Phaedrux One thing that is really throwing me is that I am using a 16 toothed pully and gt2 belts with a 2mm pitch, from this my esteps should be 100, however, when moving the z axis its more like 4, but the x and y axis are moving almost double what their intended value is. Ideas?

  • Moderator

    If your steps per mm should be 100, why are they at 80 in your config?

    M92 X80.00 Y80.00 Z80.00 E837.20 ; set steps per mm

    Are you sure they are 16 tooth pulleys? Won't hurt to count the teeth to verify. Are the motors 0.9 or 1.8 degree? Are all the motors the same? Are all the pulleys?

  • @Phaedrux I went over everything and pulled the printer apart and started fresh, took a while but was worth it, found that the belt tensioning method I have used had slackened when the motors where moving, after repairing this I am now getting the correct movements (I had uploaded the wrong config file before hand, 100 steps was correct.) I now have a new error but the end is near! I am getting this error when trying to run compensations for the print bed.

    Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
    25 points probed, min error -2.413, max error -1.900, mean -2.177, deviation 0.143
    Height map saved to file 0:/sys/heightmap.csv

  • Moderator

    That error would indicate that you are not using the probe to do a G30 to locate the bed before you have run the G29.

  • @Phaedrux Ok that fixed the issue!

    Next issue is G32 for the bed compensation

    I am getting this error

    Error: Auto calibration failed because probe point P0 was unreachable using the current delta parameters. Try a smaller probing radius.'

    How do I get it to use a smaller probing radius?

  • Moderator

    It's possible it's talking about the probing radius in M557 used for the G29 mesh grid, but you're getting that when running G32 which runs bed.g

    ; bed.g
    ; called to perform automatic delta calibration via G32
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 25 2020 02:54:46 GMT+0100 (British Summer Time)
    M561 ; clear any bed transform
    ; Probe the bed at 3 peripheral and 3 halfway points, and perform 6-factor auto compensation
    ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
    G30 P0 X0 Y279.9 H0 Z-99999
    G30 P1 X242.4 Y-139.95 H0 Z-99999
    G30 P2 X-242.4 Y-139.95 H0 Z-99999
    G30 P3 X0 Y139.9 H0 Z-99999
    G30 P4 X121.16 Y-69.95 H0 Z-99999
    G30 P5 X-121.16 Y-69.95 H0 Z-99999
    G30 P6 X0 Y0 H0 Z-99999 S6
    ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
    ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

    So I think we need to review this section:

  • @Phaedrux Awesome that's sorted! I am having one last issue! It's a strange one, I am losing connection to the printer every now and then, its completely random and I am continuously monitoring my internet speeds and having no drops, It's connected via Ethernet over TP-Link powerline boxes, I can only think they would be causing the issue but wanted to go over every option before having to move the printer into another room.

  • Moderator

    Hard to say. Doing a comparison test with direct connection might be the easiest way to find the culprit.

  • administrators

    I use a TPLink Powerlink adapter to reach one part of the house, and it regularly loses the connection for a short while.

  • @dc42 Alright thanks! Guess its time to properly run ethernet connections to the rooms, another question though! I have run the bed compensation however it doesn't seem to incorperate the new data when doing any prints, is there some command I need to run in my slicing software to get it to do this or a piece of G code I need to put into the start command or should it automatically do it when any print begins?

  • Moderator

    @Bewaren said in Delta Printer calibration issue:

    is there some command I need to run in my slicing software to get it to do this or a piece of G code I need to put into the start command or should it automatically do it when any print begins?

    When you run G29 the heightmap is saved to the SD card and compensation is applied. This only lasts until the printer is power cycled. So you can either run the G29 before every print, or if the bed is stable, you can simply load the saved heightmap before the print begins by adding G29 S1 to your slicer start gcode after the printer has been homed.

Log in to reply