Best posts made by Hornetrider

Hi

I have been scrolling thru some interesting approaches to calibrate the printer for different parameters.
In one thread there has been an approach for Pressure Advance that, in my opinion, goes in the right direction.
https://forum.duet3d.com/topic/6698/pressure-advance-calibration?_=1578666654636
thx @DigitalVision

Can such scripts also be used for determining the optimum values for:

• acceleration
• jerk
• simultanious speed changes
• speeds
• print speeds
• obviously pressure advance
• dynamic acceleration control
• non linear extrusion
  etc.

My main interest is to learn from your knowledge and experience and to find out:

• which parameters do make sense to be tested this way?
• are there any limitations, and if so which?
• the right sequence of parameters to be tested?
• how could an output be generated?

Or, maybe has somebody run a kind of DOE (Design of Experiment) to find the right parameters for the printer, instead of running hours of try and error..?

Looking forward for your input

no, this one:
https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board

@Phaedrux

see here:
https://forum.duet3d.com/topic/18601/panel-due-hanging-up-after-loss-of-wifi

UPDATE

Fault found.

As the temp signal was always spiking below the set-point I wasn't sure about the source. But a new 2000 spike brought me back on track...
In the end the cable from board to thermistor had a failure. Just connected a new on the fly and the signal was rock solid again.

I also connected the frame of the printer to Earth, this already lowered the spikes but it also brought me the 2000er..

So, in the end I also installed the BLTouch that I had in stock, now the mesh is also free of spikes...

Thank you all for your support.

@dc42

Thanks for the hint.
I have checked with a spare BLTouch (older one with metal pin) and found that something with the cables was not good.
Re-Cabled the signal line (white/black) with a brand new cable et voila, it's working again.

I think I will have to re-do all the cabling to assure functionality....but for now it's working.

Thanks for the support.