Auto calibration error

yatinsd

I upgraded my duet wifi V1.03 to Firmware version 2.02 RC4, including the web interface firmware to 1.22.5 and duetwifi server version 1.21. After setting the dive height and the trigger height i attempted auto delta calibration. The results were as follows:
Calibrated 7 factors using 16 points, deviation before 2.044 after nan
I attempted it again but as in the picture all values of x, y & z went random. Do anybody nows what is it? I have a suspicion that i accidentally deleted all my macro files including the ones that were pre stored from factory. Kindly help me identify the reason and if possible any solution.
TIA

dc42

If you power up the printer and then home it, does the head position read sensible values? If not (e.g. if it shows the 9999.0 values in your image) then your M665 delta parameters are incorrect.

If it does show sensible values, first check that the M665 L parameter matches the length of your rods, then try increasing the dive height (M558 H parameter) to a large value (e.g. 30) as if you are doing first-time delta calibration, and run auto-calibration again.

yatinsd

Mine is a delta printer. When i turn off the power then turn it on and then home it, it shows actual carriage height of 336mm. But once i auto calibrate and then home it shows head values of 99999.99 on all x, y &z( can it be because of factory saved macros?). I have checked my rod length and delta radius quite a times but still it reads the bed surface as convex upto 5mm on extreme edges. I have checked the bed seperately on dial guage it is showing a surface roughness of 0.1mm, also i have verified the frame of the printer quite a times and it was acceptably square within 1-2mm error. I dont know where i went wrong? I am already using dive height 30mm.

dc42

Please post your config.g and bed.g files.

Are you sure that the XYZ steps/mm are set correctly?

yatinsd

@dc42 yes I have checked the steps/mm using height guage they seem fine.1_1542559933424_config.g 0_1542559933424_bed.g

yatinsd

@yatinsd said in Auto calibration error:

@dc42 yes I have checked the steps/mm using height guage they seem fine.1_1542559933424_config.g 0_1542559933424_bed.g

also when i tried to auto calibrate it again it said z probe already triggered but as i saw z probe output was 0. also after updating there is something weird happening that when i try to move the head manually it just updates the position in web interface but did not move.

dc42

Your M665 command in config.g says the delta radius is 175mm and the rod length is 218mm. These values are not plausible. As the printable bed radius is set to 85mm, I suspect that the delta radius of your printer is much lower than 175mm. A typical delta radius is around half the rod length.

yatinsd

@dc42 I see that was indeed wrong i entered the printer radius than delta radius(which came out to be 125mm), I rectified it and got the following result:
Calibrated 7 factors using 16 points, deviation before 3.808 after nan.
But still after the calibration and then home the header position goes random(99999.99). What is the issue behind this, can the macro files that were already on duet from factory which i accidentally deleted be the reason?

dc42

@yatinsd, I think bed probing must have failed but the firmware didn't realise that. Is is definitely probing within the confines of the bed?

Please post your current config.g file and the bed.g file.

yatinsd

@dc42 0_1542626982241_bed.g 0_1542626988960_config.g , and also after sometimes it stops responding on web interface for head position manual change(this happened only after i updated the firmware first to 2.02 rc3 then to rc4 with suitable wifi server web interface versions.

dc42

Please try using S6 on the final G30 command in bed.g instead of S7. The 7-factor calibration may not work well if the calibration is a long way out to start with. Also we recommend use of either 6- or 8-factor calibration.

yatinsd

@dc42
This happened when i tried auto calibration again to have converging results after one round of calibration.(I have shifted to 6 factor calibration)0_1542646205637_bed.g
Below is the result of first round of calibration:
Calibrated 6 factors using 16 points, deviation before 3.775 after nan
Also when it homes for auto calibration not all axis are homing only one i have to do them manually first.

dc42

@yatinsd said in Auto calibration error:

Also when it homes for auto calibration not all axis are homing only one i have to do them manually first.

See https://duet3d.dozuki.com/Wiki/FAQ#Section_When_I_try_to_home_my_printer_sometimes_the_carriage_or_carriages_move_only_part_of_the_way_towards_the_homing_switches_and_I_have_to_command_it_to_home_again_to_make_it_go_all_the_way. The failed homing may explain the problem.

yatinsd

@dc42 now it homes but still there is this probing error.

dc42

Do you get probing error messages the first time you run auto calibration? I was under the impression that you only got them the second and subsequent times that you ran it.

yatinsd

@dc42 i got the error only the second time, first time it ran fine with below results:
Calibrated 6 factors using 16 points, deviation before 3.775 after nan

dc42

@yatinsd, please sort out the homing issue first - see my earlier reply. Then see whether the auto calibration problem persists.

yatinsd

@dc42 yes I have already sorted homing issue, but auto calibration problem is still persisting!

dc42

Does your config-override.g file have M665 and/or M666 commands in it? If so, delete them.

yatinsd

@dc42 there is no config override file being created after auto calibration! can this be due to the macro files that i deleted accidently?

dc42

Auto calibration does not in itself create a config-override.g file; but you can send M500 after running auto calibration to save the values.

So was there a config-override.g file on your system, or not?

yatinsd

@dc42 I cannot see any such file!

yatinsd

@dc42 I tried M500 command still the same issue the when home after 1st auto calibration the head position goes random for xyz. Though now the config override file is created.

yatinsd

@dc42

dc42

Please can you change the S parameter on the final G30 command to S-1. This will cause the firmware to report the height errors without making any changes. Then report the height errors here.