Posts made by Egris

Tested fw 3.3 beta 2 on my rotary delta. Has there been a change to Segments per second for this kinematic? X/Y G1 moves look like there is a very low segments per second value usesd for straight lines.

With the older 3.3 version its working fine

Did a first Print after setting up autocalibration, mesh bed compensation and preasure advance..
I´m quiet happy with the result.

Thx again for looking into it

picture of the print

@dc42 hello dc42, currently i think the calibration code works! I played again with the radius in which it probes the points and now it looks quiet good . I have one question.
Im using the fw 3.3 and when i do a mesh calibration the header of the hightmapfile is as follows..

axis0,axis1,min0,max0,min1,max1,radius,spacing0,spacing1,num0,num1
X,Y,-140.00,140.00,-140.00,140.00,-1.00,20.00,20.00,15,15
0.115, 0.139, 0.118, 0.101, 0.075, ....

When i want to check the graph on the webinterface it says invalid hightmap..

when i change the header to

xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
-140.00,140.00,-140.00,140.00,-1.00,20.00,20.00,15,15
0.115, 0.139, 0.118, 0.101, 0.075, ....

It shows me the graph output.

Which format will the firmware need to do the compensation correctly?

@dc42 after several calibrations the values will stop at a certain level and are adjusted each cycle a little bit higer / lower. After the calibration i moved the head to a bit above Z0 and moved in X direction. I noticed a bowlshape movment. So i adjusted the rod lenght manually, did another calibration cycles and now i have quiet a steady linear movment above the bed

Then i did a G29 Mesh calibration..
225 points probed, min error -0.188, max error 0.428, mean 0.017, deviation 0.094

When i want to look at the graph it says Invalid Height Map. Im not sure why this will happen. The File is saved to the sd card

heightmap.csv

@dc42 did a Autocalibration. Result is as follows:

M669
Kinematics is rotary delta, arms (190.000,190.00,190.000)mm, rods (393.500,393.500,393.500)mm, bearingHeights (422.008,422.01,422.008)mm, arm movement -90.0 to 46.5°, delta radius 45.480, bed radius 212.1, angle corrections (59.839,59.430,60.000)°

M666
Endstop adjustments X-0.82 Y-1.04 Z-1.47°

Start Values:
;M669 K10 U190.0 L393.5 R45 A-90.0:46.50 H418.8 X60, Y60, Z60 B212.132 (59.839,59.430,60.000)
;M666 X0.0 Y0.0 Z-0.28

@dc42 thanks alot for your support. Bed probing is working now . I will try the autocalibration function and write a feedback how it works.

i can do that test probably tomorrow. I think i damaged my Z_Probe_In Pin by the 5V Signal of the BLtouch. My Duet2 probably was older than the revision that can handle 5V on that Pin. . Is there a possibly to use another analog pin for my Z-Probe? I orderd a spare one

@dc42 said in rotary delta + mesh compensation | Strange Z-Lift:

Move the nozzle to a point off-centre e.g. X0 Y50 Z10. Then command the nozzle up (e.g. to Z50) and check that the movement is vertical. Next, command the nozzle to X0 Y50 Z10 again, but after that send G91 Y50 Z10 (i.e. tell the machine where it is at, giving it the same coordinates that it thinks it is at). Then command the nozzle up to Z50 again and see if the movement is still vertical.

tested it and it works like it should. Z-Movment is vertical

@dc42 1. Are you saying that when the machine has been calibrated manually so that good prints are possible, the Z-lift moves during mesh bed probing are not vertical?

Yes thats true. In the Center of the Bed the Z-Lifts are "more" vertical than they are getting to the edges of the bed.

If i set my grid-probing to X-145:145 Y-145:145 the first Probe is at X-145 Y-145. Everything works fine until the Z-Lift. When Z is lifted the head moves to abaout X-145 Y145 in a not coordinated move. When it arrives there the head will move to the next grid point at X-125Y-145. On that 2 moves it crashed the nozzle into the bed

i looked into the Statemachine for bed-probing in Gcodes 4 but couldn find any hint.
before the Z-Lift there is called the Function SetMoveBufferDefaults(). Could there be somthing reset?

@dc42 at the moment i cant confirm weather the mesh compensation is working or not. For me it was not possible to finish the grid probing. At the outskirts of the bed the Z-Lift is doing really fast moves to the other side of the bed. What i can confirm is that printing without the compensation is working really well.

Probing a single point changes / effects the the machine coordinate sytem. After a G30 when i whant to move lets say only in Y-Direction, the move is in Y and Z direction like in that last video.

Looking forward to solve this Problem together. Thanks alot for looking into it.

@dc42 thank you very much for looking into my problem!
Here is my config.g File

config.g

and i did a drawing of the actual wiring layout

; Rotary Delta Config
M669 K10 U190.0 L393.5 R45 A-90.0:46.50 H419.5 X60, Y60, Z60 B212.132
M666 X0.0 Y0.0 Z-0.28

I rotated the all 3 arm angles by 60° to line up the X/Y Axis

@dc42 After the G30 i did via Webcontrol button Y+5 5mm in Y-Direction. The Effector is moving in Y and Z direction. Could this matter?

https://youtu.be/W4afA7cdHNI

Testing it with 3.3 beta gives the same Result

@dc42 yes sure, here is a link for probing a single point

https://youtu.be/DCtipYQOzsc

-> Home Delta
-> G1 Z30
-> G1 X-130 Y-130
-> G30

Board: Duet 2 Ethernet (2Ethernet)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2 (2021-01-05)
config.g

@PCR With M557 R140 S15 got the same result for the Z-Lift as
M557 X-140:140 Y-140:140 S20..
Effector moves after first probe trigger to abaot X0 Y140.
Thanks for your help

@Egris 2 years ago i used firmware 2.x. There i managed to probe the bed with g29 in a rectangular grid

https://youtu.be/v46Gh64aN_o?t=65

@PCR I haven't tested this yet, i will give it a try

@dc42 good evening, i uploaded a short Clip where you can see the Mesh Compensatzion Probing.

https://www.youtube.com/watch?v=zwc3E4wfodQ

The Z-Lift after the probe triggers did a strange movement.
I limited the Probing to X 0:145 & Y0:145

normally i use X -145:145 & Y-145:145 but after the first trigger the effector will move to about x-145 Y145 and crash into the bed.

maybe you have any idea. It's the last problem I'm trying to solve. Thank you in advance. Great firmware, thumps up

@dc42 yes i will record a short videoclip