@Phaedrux i want to thank you. i cannot even tell you how grateful i am to have finailly figured this out. there was def a bad connection and some bad config files. problem solved, thanks guys
A bit late (my reply), but I encountered the same problem with my volcano (0.8mm nozzle, direct all metal, 2.85mm filament) and it helps, if you have a 50W thermistor and a silicone around the heating block. I had to turn the part cooling fan down to 35-40%, then when the fan kicked in, it did not throw the temp off that much. I gradually raised the fan speed afterwards.
@Oliver3d I wish you good luck. It would be interesting what speed and precision you achieve. It would be nice if you can tell the restults.
Regarding Belt drives, ball screws etc. I learned a lot from the CNC expert Möderl (EMS), you may find ideas on his pages. Unfortunatey it's only in german.
I think whilst in the getting it set up and calibrated take out the 501 a and delete or rename the config override file now is not your friend as you are making changes that that file may be overriding and giving you false results use the 6 or if you are sure your radius is correct use 4 factor even
Use a feller gauge to set your bed as best you can at a specific height like 0.1mm Move your effector around the bed adjusting the bed don’t home after calibrating as homing wipes the calibration.
I’m sure other Delta users will get involved but I had a journey getting mine calibrated which turned out to be a faulty part so if your convinced in your process being solid don’t rule out a loose idler or bolt as most of the time as I’m sure the developers will agree it’s the most common cause.
Are you heating the bed before calibration ? Ideally you are to 60c
Is your sensor accurate ? No loose wires/crimp?
Is it consistently giving the same deviation? With out changing any settings as to say if you calibrate 5 times does the deviation change?
Hope this is of help
C
@taconite i think this situation came up before. A possible cause was that mechanical advantage afforded by a low lead screw meant the motor will see very low mechanical resistance. Approximately 10% of a belt drive in your case. Phaedrux alluded to this above
I'm really bringing this post back from the dead!
Was there any progression on the use of your non-contact sensor through the Duet system? I am wanting to implement something similar for myself.
Thanks, allso found out that stratasys has a patent for ''intelligent'' tool paths, it just basicly overlaps the ends so there is no gap, how can one justify to patent a sring of gcode is beyond me.
@dc42 I guess the space time continuum waited for me to make a fool of myself and then revealing me the offset function within Ideamaker.. if it works for delta, it should work for this.
Thanks
I used to have my home call in my config.g but I was advised to not do that. So I have removed it. I just put the G30 and G29 in my starting script for my slicer. I also usually home at the start of my print files.
I was able to write a macro to actually use the stall detection to automatically calculate the probe trigger height. So I may change how I do a few things now too. But I literally figured that out last night so I haven’t really had a chance to figure out how I’ll implement it.
@justus2342 It may be faulting because each tools standby temperature is set to 0C, but then it can't get to that because the other tool is still heating the heater. Try setting active and standby temperatures to the same with G10. Are you using tool change macros (tpre, tpost, tfree), and are there any heater commands that may be tripping it up in there?
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.
@Dougal1957 It started of at about 95 and just keeps climbing. The good one was 108.5 and did not move. Hope that helps
Yes thanksdisprooves my thoughts tho I was hoping it would have been a lot higher which would have been in line with the 2000 degrees reading but the fact it starts at 95 and steadily increases does suggest it not good.