@Phaedrux said in CoreXY printing very slowly:

X500.00 Y500.00 Z200 E3000

That in combination with an errant M201 in the startup G-Code seems to have fixed it.

Probably the classic issue of taking the values from a saved Marlin config and transposing them.

Thanks for the help

Good to hear that you are making progress!

@Lampie yes, thats normal
you can either save that using M500 and make sure you have M501 at the end of your config or replace the M307 command you should already have for your bed.
when you come to tune your hotend, tune it as a tool rather than a heater, so M303 T0 S220.
move the nozzle so its about 5mm above your bed so its simulating real printing

I am still having problems with the measurement results of the different samples.
Is it due to a fallacy or are the measurement methods really different?
Or is there a problem with the firmware in the end?
Maybe one of the mods is able to help me here? ( @dc42 )

greetings and hoping for help!

kuhni

thank u for the help guys..

For anyone reading this later, this is a working macro to calibrate the Z trigger height for the Pinda/Superpinda: z_offset_calibration.txt

EDIT: one might want to heat the bed to the bed temperature that will be used for printing to get an accurate result throughout the procedure. In my case with the MK3 bed and a temperature of 85C for printing PETG the value was about 0.15mm off compared to running the macro with a cold bed.

aha ok wil do that ,thank u !👍 👍

I have finally dialed in the value. Apparently 0.11 is too much.

I printed the "toleromancer" a 0.1mm offset test print with 1mm, 1.5mm, 2mm, 2.5mm interlocking features:

0fda8999-2b59-4541-a4ab-dec4036cb1ed-image.png

This allowed me to fine tune the values with "real world" application: fitment.

0.000 didn't fit, as expected.
0.100 fit but snugly, so not optimal
0.110 fit, but with snugness on the smallest 1mm part, kind of counterintuitive

0.105 fit perfectly with 0.1mm tolerance throughout including the 1mm part.

Hereby I present you the Toleromancer:

https://www.thingiverse.com/thing:4794036

@zapta said in Resonance, spreadCycle and stealthChop:

How does this work, did you replace the Duet's firmware with a dumb version that is controlled by the Klipper SBC?

yes, you have to replace the original firmware with Klipper's. I like RRF "all is Gcode" philosophy, but over all I prefer klipper and I don't think I'll revert back, at least for now.

When I think about it, I think the last time I cleared up the ripple as you see in the height map was actually solved by swapping my magball arms around. Accumulated errors between carriage + arms+ effector made measuring arms with magballs in them unattached to the actual build a trap, I had to measure from the rail to the ball end, then from ball end to ball end, then put the arms in the right position to get most uniform pairs on a tower as well as best average length. For my magball arms (360mm haydn huntley magball arms), what threw me off was the effective pivot point. For my set at least, If I measure the arm with a 9.5mm ball stud on each end from the edge of a ball to the other edge of the ball, the firmware measurement is that distance minus 7 (plus corrections for effector/carriage errors). Why 7? Because (once again for mine at least) the 9.5mm ball is inset about 3mm into the arm, and the effective pivot is 3mm further in from the edge of the arm, leaving 3.5mm from each ball end to subtract on each side. My desire for things to work neatly kept driving me to think it'd pivot in the center of the ball stud which is not the case. Figuring that out was so frustrating I think I want to forget it again.

@Veti said in Strange bed distortion on delta machine:

strange it looked like
http://boim.com/DeltaUtil/CalDoc/Calibration.html
Tower Placement Symmetry

That, and incorrect rod length, I’d say.

Ian

@mendenmh said in Camera thermistor calibration:

I hate to argue with you, but this is the wrong approach.

Really? Most people seem to enjoy it. 😉

I'm not a thermistor expert by any means so I could be way way off.

@tekkydave Yep, mine is fake as shit. Looks like I need to get some better ones.

@dc42

Nice!

In your print layers are consistent so lines don't bulge randomly as in mine.

@dc42 in the start G code there is always homing X U Y Z. But when I enable only Left or Right extruder with G10 in the beginning, during print the tool that was not active was moving a little back and forth with Y-axis changing direction.
Then I found a faulty mainboard
......
The whole time there was no unactivated axis motor

So I think it is now sorted with new mainboard

@TiToMoskito its taking your probe offsets into account.
So you ask for a nozzle position of X70 Y10 and it moves so the probe is over that position, which is X23 Y26

I re-posted your config.g file here.

; Configuration file for Duet WiFi (firmware version 2.03) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu Mar 04 2021 17:26:50 GMT+0530 (India Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"fabforge v1" ; set printer name ; Network M551 P"fabforge" ; set password M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S0 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X125.98 Y125.98 Z1600.00 E436.54 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X7200.00 Y7200.00 Z600.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1200 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X210 Y210 Z210 S0 ; set axis maxima ; Endstops M574 X1 Y1 Z2 S1 ; set active high endstops ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:180 Y15:180 S20 ; define mesh grid ; Heaters M305 P0 T100000 B3950 R4700 ; set thermistor + ADC parameters for heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M305 P1 T100000 B3950 R4700 ; set thermistor + ADC parameters for heater 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M106 P0 C"Part Fan" S0 I0 F500 H-1 ; set fan 0 name, value, PWM signal inversion and frequency. Thermostatic control is turned off ; Tools M563 P0 S"Head 1" 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 0C ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

Keep in mind that this is a mechanical, fluid dynamic, and thermal dynamic problem.

If you increase extrusion rate, then one one or more of the following needs to change.

increase the hot end temperature lower the part cooling fan speed increase the nozzle diameter

the extrusion/flow rate multiplier (slicers have various names for it) is nothing more than a fudge factor that allows you to make a tweak without changing one of the above.

Calculating your e steps at 1 mm/s will minimize the the fluid dynamic and thermal dynamic variables at play.

If you want to completely remove fluid dynamic and thermal dynamic variables, disconnect the extruder from the hotend. That way the only thing you're dealing with are mechanical variables.

Have you tried without the conditional gcode setup?

@dc42 Ok, Thank you

The Part Fan is one 5015 Blower and the Hotend cooling Fan a 40mm Sunon that is running for testing between 40 and 100 %