jimcnulty / fdc Goto Github PK

I am looking over the macro but Im unsure what the issue is.

I get these errors:

Error evaluating 'gcode_macro _FDC:gcode': gcode.CommandError: ref_temp or current_temp is out of range 26.7, 29.1

Maybe you have an idea what I have done wrong?

Cheers!

Hi There!

So you say:

X gantry on the opposite side of the X endstop at the end, touching the aluminum
    I know, it's a pain to find a way to install it, but it's the only place to put the sensor that will give accurate results
    Other places are a gamble, try it if you want - if it works, great, if it doesn't, you know why

Don't mind me asking but can you explain why that particular spot is the only place that gives accurate results?

I'm trying to think why the Y gantry extrusion, say somewhere in the middle, isn't just as good a spot or even better?

Thanks!

Maybe its supposed to happen, but this is the latest output from the script, from like 30 minutes ago.

Measuring (#39)...Gantry/bed already trammed.      
Tramming gantry/bed...DONE
DONE

I think I noticed the last few meshes had longer pauses in between them (is that correct?) but now it seems to have stopped taking meshes entirely.

Any ideas please?

I think one of the biggest reasons this hasn't seen more widespread adoption is that it is cumbersome to switch between profiles for different printing temperatures or different setups such as open vs closed enclosure. Adding a script to allow switching between profiles such as how bed mesh works natively in klipper would be a huge improvement. I think it might also be possible to implement this using a macro in klipper but it would probably be a bit more involved for the end user.

I only have a clone BLTouch on hand for my flying bear reborn 2, and I'm not getting a lot of help configuring it, so I thought I might be able to use this without a mesh. is that the case

Im at the point of copying the generated config and then it says this:

Paste if after the string ...-- SAVE_CONFIG --...
And after the default bed mesh
If you don't have one just copy your first bed mesh and change the name

I don't have one so I can copy the one #*# [bed_mesh 31.3], which is the first one.

But what do rename it to? Just [bed_mesh] without a temperature, or some low ambient room temp?

Thanks! Can;t wait to try it out 😋

Point 11 here says to Edit the macro with the min max temp, step and z_height_temps dictionary that was printed when you ran the script.

The script on the Pi when starting the measurements, or processing the results on the local PC?

I checked both outputs from when I started them, but I don't really see which part I need to take?

The Pi started as follows:

pi@vcore-3:~/FDC $ nohup python3 measure_thermal_behavior.py 0.1 > out.txt &
tail -F out.txt
[1] 132124
nohup: ignoring input and redirecting stderr to stdout
Starting!
Homing...DONE
Gantry/bed already trammed.
Tramming gantry/bed...DONE
Setting heater targets: Bed=105.0 degC; Tool=255.0 degC
Parking toolhead at Z=240.0mm for bed heating...DONE
Waiting for bed to reach 105.0 degC...DONE
Heatsoaking bed for 0min...DONE                     
Starting!

And the local script to process did this:

Hr46ph@mylocalpc ~/fdc_meshes/FDC $ python3 generate_FDC_meshes_z_heights.py thermal_quant__2023-04-23_14-16-49.json 0.1 --filter_noise
Normalizing mesh 31.3 to middle zero, drift: 0.016875
Normalizing mesh 34.1 to middle zero, drift: 0.014062
Normalizing mesh 36.5 to middle zero, drift: 0.014375
Normalizing mesh 38.8 to middle zero, drift: 0.012812

Thanks! Almost there 😃

I'm probably a numpty :P but I find the Kipper docs somewhat lacking on z_thermal_adjust.

Could you provide some sane defaults please?

I would assume the min_temp and max_temp are safeguards for the frame thermistor? So would 0 and 100 be good?

Are there any other required settings in that section?

Thanks for the help!