[not yet solved] Tevo Little Monster DuetWifi errors
-
-
Some post above there is a calibration that look like very different
-
I presume you ran auto calibration before you generated that height map. Did you run auto calibration (G32) before generating the height map (G29)? Assuming that you did, what was the reported calibration deviation; and are you using the same bed.g file that you published in your earlier post in this thread dated 21 September?
-
Hi dc42,
This is the actual bed.g :
*; bed.g
; called to perform automatic delta calibration via G32
;
M280 P3 S160 I1 ; clear all BL-touch errors
M561 ; clear any bed transform
; generated by RepRapFirmware Configuration Tool on Mon May 22 2017 22:56:20 GMT-0400 (Eastern Daylight Time)
G28 ; home all tower
G0 Z400 ; Move while giving the BLTouch time to clear the error
; Probe the bed at 6 peripheral and 0 halfway points, and perform 3-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.
M98 Pdeployprobe.g
G30 P0 X0 Y129.9 H0 Z-99999
G30 P1 X112.5 Y64.95 H0 Z-99999
G30 P2 X112.5 Y-64.95 H0 Z-99999
G30 P3 X0 Y-129.9 H0 Z-99999
G30 P4 X-112.5 Y-64.95 H0 Z-99999
G30 P5 X-112.5 Y64.95 H0 Z-99999
G30 P6 X0 Y0 H0 Z-99999 S3
; 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)M98 Pretractprobe.g
G29
G28
;G1 X0 Y0 Z150 F15000 S2*Turning on the printer the M122 didnt load the mesh , so I do all the time the calibration and after this the M122 report "mesh" for the bed compensation.
Bed compensation in use: mesh
Bed probe heights: -3.115 -2.859 -2.963 -3.287 -2.919
Yep ,I do the auto calibration from the web interface pressing "auto delta calibration" , then the result is that image you can see this post above.
They look to me strange number...are too big... -
Boh...I mean boh...just because i didnt know the cause>effect related to what im doing...anyway...
I changed the bed.g coordinates for the calibration from actual to the one taken from the Eric files and this is the result LOL Maybe the S6 compensation or calibration point , against the S3? More point to read?
old ones:
G30 P0 X0 Y129.9 H0 Z-99999
G30 P1 X112.5 Y64.95 H0 Z-99999
G30 P2 X112.5 Y-64.95 H0 Z-99999
G30 P3 X0 Y-129.9 H0 Z-99999
G30 P4 X-112.5 Y-64.95 H0 Z-99999
G30 P5 X-112.5 Y64.95 H0 Z-99999
G30 P6 X0 Y0 H0 Z-99999 S3
new ones:
G30 P0 X0 Y132.28 H0 Z-99999
G30 P1 X121 Y69.86 H0 Z-99999
G30 P2 X129.9 Y-75 H0 Z-99999
G30 P3 X0 Y-150 H0 Z-99999
G30 P4 X-129.9 Y-75 H0 Z-99999
G30 P5 X-121 Y69.86 H0 Z-99999
G30 P6 X0 Y59.15 H0 Z-99999
G30 P7 X56.09 Y32.38 H0 Z-99999
G30 P8 X64.95 Y-37.5 H0 Z-99999
G30 P9 X0 Y-75 H0 Z-99999
G30 P10 X-64.95 Y-37.5 H0 Z-99999
G30 P11 X-56.09 Y32.38 H0 Z-99999
G30 P12 X0 Y0 H0 Z-99999 S6
-
Yes, using S6 normally improves the delta calibration by calibrating inaccuracies in the tower positions too.
When you run G32 several times in succession, what deviation does it converge to?
-
@dc42 said in [help] Tevo Little Monster + DuetWiFi + DuetTouch7" errors:
converge
It look like always between max of 0.1x/0.1x with S6.
I tried also S9 and this is the result , of max of 0.1x/0.0x :
With S6 there were still trouble. The print with big base come really attached from one side and few attached to the other.
edit:
Still with S9 the problem remain the same (also if the mesh seems a little better) . On one side of the glass the print stay too high and the other low. Uff...so frustrating. The mesh seems loaded.Suggestions?
ps: extruder arrived and mounted with 0.9 motor.
-
What type of Z probe does your machine have? If it's not a nozzle contact probe then the problem may be caused by effector tilt.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42
I have the BL-Touch , original one mounted on the Tevo LM.
Is strange because with the original components there was not those difference. So I can image that is a software problem. If the calibration would be correct the 1srt layer should stick like expected in all its parts...instead it do not. -
If it's a BLTouch then the probe must be offset some way for the nozzle, so I am 99% sure that the problem is that the effector tilt is varying with XY position. It's very hard to get the geometry of a delta printer sufficiently accurate to eliminate this completely.
You can test this by measuring the trigger height of the Z probe at different XY positions.
-
Thanks...I'll check it and I'll report the results...
In the same time I'll try to understand better other stuffs related to this..
https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation -
I tried make good homework ...but i miss still something.
As the file Eric posted I tried do the same. Now the bed.g look like this:; 7 points, 6 factors, probing radius: 150, probe offset (0, 0)
G30 P0 X0.00 Y150.00 Z-99999 H-0.080 ; trigger height 1.640 > done
G30 P1 X129.90 Y75.00 Z-99999 H0.320 ; trigger height 1.880 > done
G30 P2 X129.90 Y-75.00 Z-99999 H0.240 ; trigger height 1.800 > done
G30 P3 X0.00 Y-150.00 Z-99999 H-0.020 ; trigger height 1.540 > done
G30 P4 X-129.90 Y-75.00 Z-99999 H-0.262 ; trigger height 1.298 > done
G30 P5 X-129.90 Y75.00 Z-99999 H-0.320 ; trigger height 1.240 > done
G30 P6 X0 Y0 Z-99999 S7 ; Bed center, main trigger height 1.560
; For G30: 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 center of bed); Bed center, main trigger height 1.560 - sottrarre all'altezza centrale le altezze per ciascun punto e mettere la differenza positiva o negativa come altezza nei vari G30.
I taken 3 times all the 7 point. I commanded down the head close the bed and lowered by 0.05 steps against the glass. I noticed that if i use bigger step the head one time against the glass lift a little on xy , so I used the smallest steps.
And the result is this:
BUT the result in printing is identical.... one side barely stick , the other stick like hell.
I tried also see if the BLtouch was aware of changing bed high. I removed two spacer that sustain the bed (screwing a little) and this is the result:
I'm stuck.
Also if I manually level the bed with spacer to make the calibration look like perfect , I'm sure the printing will not go well. As mentioned the delta printer have more tolerances so the solution should be where you suggest but it didnt work
-
Eric add those line in the comment of the bed.g :
- entered in config-override.g G31
And this is the config-override.g :
; This is a system-generated file - do not edit
; Delta parameters
M665 L397.048 R156.896 H524.725 B175.0 X0.206 Y-0.111 Z0.000
M666 X-0.295 Y0.233 Z0.062 A0.00 B0.00
; Heater model parameters
M307 H0 A93.8 C266.0 D9.4 S1.00 B0
M307 H1 A372.4 C90.9 D4.4 S1.00 B0
M307 H2 A340.0 C140.0 D5.5 S1.00 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 B0How he calculated the new parameters for the M665 ?!?!
-
M665 and M666 values are obtained though using delta calibration. They are written to config-override.g through the command M500, and then loaded when the printer starts up as long as M501 is at the end of your config.g (which it is from your earlier post). You can see what values are currently set from M666 and M665 by typing the commands into the console with nothing after them:
Are you running delta calibration before trying to get the mesh bed compensation working? It looks to me like you are showing pictures of the mes bed compensation but not the results of delta calibration. you may need to run delta calibration a few times to get it to converge.
Use the command G32 in the gcode console a few times and post the results.
-
Hi Tony,
thanks for your time too...
5 tries with cold bed :
First G32 cold bed
Calibrated 7 factors using 7 points, deviation before 1.534 after 0.000
37 points probed, mean error 0.003, deviation 0.068
Height map saved to file heightmap.csv
Second G32 cold bed
Calibrated 7 factors using 7 points, deviation before 0.033 after 0.000
37 points probed, mean error -0.000, deviation 0.064
Height map saved to file heightmap.csv
Third G32 cold bed
Calibrated 7 factors using 7 points, deviation before 0.052 after 0.000
37 points probed, mean error 0.047, deviation 0.063
Height map saved to file heightmap.csv
Fourth G32 cold bed
Calibrated 7 factors using 7 points, deviation before 0.034 after 0.000
37 points probed, mean error -0.001, deviation 0.059
Height map saved to file heightmap.csv
Fifth G32 cold bed
Calibrated 7 factors using 7 points, deviation before 0.018 after 0.000
37 points probed, mean error -0.002, deviation 0.062
Height map saved to file heightmap.csv
Now 5 tries with hot bed and hot nozzle :
First G32 hot bed
Calibrated 7 factors using 7 points, deviation before 0.130 after 0.000
37 points probed, mean error -0.021, deviation 0.056
Height map saved to file heightmap.csv
Second G32 hot bed
Calibrated 7 factors using 7 points, deviation before 0.066 after 0.000
37 points probed, mean error 0.030, deviation 0.063
Height map saved to file heightmap.csv
Third G32 hot bed
Calibrated 7 factors using 7 points, deviation before 0.055 after 0.000
37 points probed, mean error 0.037, deviation 0.064
Height map saved to file heightmap.csv
Fourth G32 hot bed
Calibrated 7 factors using 7 points, deviation before 0.049 after 0.000
37 points probed, mean error 0.000, deviation 0.057
Height map saved to file heightmap.csv
Fifth G32 hotbed :
Calibrated 7 factors using 7 points, deviation before 0.065 after 0.000
37 points probed, mean error 0.038, deviation 0.062
Height map saved to file heightmap.csv
The M665
Diagonal 407.831, delta radius 159.010, homed height 523.247, bed radius 175.0, X 0.508°, Y 0.646°, Z 0.000° -
I have added the M665 to the config.g then I restarted the printer and run twice the G32 with hotted bed , but this doasnt change a thing... the problem still remain the same:
I settled the 0.1 offset. If I set 0.05 i go thorough mouse bite even with the new Bondtech extruder.
Still something is not well settled ...
-
@giostark you should run G32 a few times, until it gets as close as possible to converged. Leave the mesh bed levelling out for now.
Once you have it converged as close as possible then you can do mesh bed levelling if you need to. They are not the same thing.
As you are using a BL touch off to one side it is worth manually checking the probe trigger height at each point you are using for G32 in bed.g. Start by confirming that probe correctly sets Z0 in the bed center. Then move to each of the other point and check the Z trigger height. If you see any difference (cause by effector tilt) the capture that in the H offset in the G30 commands in bed.g
Cheers
Tony
-
Sorry , but is not what I have done already some post above?
After I change the M665 with the above content the new grid look like this . It seems more regular than before:
Sorry again , what you mean as "converged"?
I have done :
1)z-probe for the center point.
2)for all the 7 points taken the trigger height and subtracted it at the center trigger height and added the numbers int the bed.g as above posted.
3)changes the M665 in the config.g with new data calculated by the firmware.
4)run the G32 several times (auto delta calibration) and also runt the auto grid calibration.
5)tried to print with the above results, even with the map of this post.I have not understood your last sentence....
-
Is arriving also the BLTouch-Smart V2... lets see if I can solve those problems...
-
@giostark I think you are making progress!
Step 4 above: run the G32 several times (auto delta calibration) . That is where you should see the value with deviation before and after reduce after each step once it has reduced enough that it's no longer changing "much" between each step then it's converged. The "much" depends on your system and how repeatable it is.
Please show the output of G32 after running it a few times.
Cheers
Tony
