-
@Orang_ said in Rotary delta calibration not implemented?:
M203 X6000 Y6000 Z6000 ; set maximum speeds (mm/min)
Try to halve the speed values to 3000
-
sorry I have M203 X1000 Y1000 Z1000
-
could this have something to do with that t2 tool? the printer is set up so that 0 is the effector, or rather the fisheye center
-
@Orang_ said in Rotary delta calibration not implemented?:
; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P2 S"2rr" D0 H1 F0 ; define tool 2 G10 P2 X0 Y0 Z-23.3 ; set tool 2 axis offsets G10 P2 R0 S0 M563 P5 S"TEST" D0 H1 F0 ; define tool 2 G10 P2 X0 Y0 Z-29.3 ; set tool 2 axis offsets G10 P2 R0 S0
You mean this?
Why does it go from P0 to P2 then P5, but P5 still uses G10 commands with P2?
-
@Phaedrux said in Rotary delta calibration not implemented?:
Why does it go from P0 to P2 then P5, but P5 still uses G10 commands with P2?
I switched to rrf firmware not long ago
-
@Phaedrux said in Rotary delta calibration not implemented?:
You mean this?
I mean that during normal movement the printer moves correctly, during arc calibration you can see it on the video. it can be related to the offset of the tool and the sensor
-
I'm not exactly sure how the -Z offset on tool2 is going to have an effect. I'm not even really sure what the reasoning or intension is there.
You're using an IR sensor though, so you should have an XY offset configured for it in G31
G31 X0 Y0 Z33.385 P25
And the Z trigger height should be calibrated.
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
I would try simplifying your tool definitions to
; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0CAnd then select T0 at the end of config.g instead of T2
Then try G32 again.
-
https://github.com/Duet3D/RepRapFirmware/blob/dev/src/Movement/Kinematics/RotaryDeltaKinematics.cpp
221 bool RotaryDeltaKinematics::DoAutoCalibration(size_t numFactors, const RandomProbePointSet& probePoints, const StringRef& reply) 222 { 223 return true; // auto calibration not implemented yet 224 } 225 226 // Write the parameters that are set by auto calibration to a file, returning 227 true if success 228 bool RotaryDeltaKinematics::WriteCalibrationParameters(FileStore *f) const 229 { 230 return true; // auto calibration not implemented yet 231 }
-
I understand correctly that there is no calibration for rotary delta?
-
@Orang_ said in Rotary delta calibration not implemented?:
I understand correctly that there is no calibration for rotary delta?
That is correct. The problem is that there are potentially many calibration variables for a rotary delta. For example, there are two pivot locations (like the tower position corrections for a linear delta), three upper arm lengths, three lower arm lengths, three pivot height corrections, three homing position corrections, and the delta radius. That's 18 parameters. It's unlikely the by probing a flat bed and measuring the height errors, it would be possible to calibrate all of these. However, if some of these are known to be accurate (for example, if all the arms are manufactured to precise lengths) then it may be possible to auto-calibrate the remaining parameters.
I can try adding auto calibration when I have time, but it might not give very good results.
-
@dc42 said in Rotary delta calibration not implemented?:
That is correct. The problem is that there are potentially many calibration variables for a rotary delta. For example, there are two pivot locations (like the tower position corrections for a linear delta), three upper arm lengths, three lower arm lengths, three pivot height corrections, three homing position corrections, and the delta radius. That's 18 parameters. It's unlikely the by probing a flat bed and measuring the height errors, it would be possible to calibrate all of these. However, if some of these are known to be accurate (for example, if all the arms are manufactured to precise lengths) then it may be possible to auto-calibrate the remaining parameters.
I can try adding auto calibration when I have time, but it might not give very good results.Thank you, I really like your firmware, if there are any changes with the calibration, please let me know, I would be happy to test it. Also there is not a big group of people who own similar printers I think they will also support it.
-
I'll just make @gloomyandy aware of this thread
-
@Orang_ on another note. Is there a good project for building one? Saw this one this week: https://www.youtube.com/watch?v=Tj1KAbq99dc
-
@PCR I have one of these https://www.youtube.com/watch?v=COUdIsoDgMw&ab_channel=AlexKorvinWorkshop
-
-
@jay_s_uk but smoothie doesn't work quite right.
-
@Orang_ who said anything about smoothieware?
-
@jay_s_uk I think he's saying smoothie (which runs on that thingiverse-link printer) doesn't work, so he's looking at Duet firmware.
-
The project specified in the link works on smoothie. but I reconfigured it to rrf
-
@Orang_ ah, ok. no problem