Auto calibration error

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.

yatinsd

@dc42 I did the same as you said but the problem has just dissapeared now, i dont know how( i am able to auto calibrate it one after other). But there is one peculiar thing happening that ( I deleted the config-override file before i started the auto-calibration) now when i try and pass the M500 command no config override file is generated.

yatinsd

@dc42 it is now showing the config override file as well!

dc42

@yatinsd said in Auto calibration error:

@dc42 it is now showing the config override file as well!

I'm glad it's now working for you. If it goes on working, please mark this thread as Solved by editing the title.

Duet Web Control doesn't update its file lists automatically. You often need to click the Refresh button to see the latest changes. This may be why you didn't see the config-override.g file at first.

yatinsd

@dc42 0_1542832005147_config-override.g This file is generated after auto calibration 8 factor. when i input S1 it is fine, but when i use 8 factor calibration head values go random(read 999.99) all of a sudden. I need to do 8 factor because my bed is showing convex(4.5mm error at extreme edge) still but isnt(checked seperately).

dc42

I suggest you connect a PC running e.g. YAT or Pronterface to your printer via USB, send M111 S1 P4 to enable Move debug, then run auto calibration. It will send details of the calibration calculations to the PC. If the auto calibration results in nans and you post that output here, I may be able to work out what is going wrong.