[FR] Linear Advance Pattern - Link printed elements to allow analysis of the print surface (and ease removal)

[gpread]

Is your feature request related to a problem? Please describe.

This is not technically about the firmware itself, is a request to enhance a tool in relation to configuration of the firmware.

Its an enhancement request for the linear advance calibration pattern generator(https://marlinfw.org/tools/lin_advance/k-factor.html)

This is fundamentally already a good tool but it can be a bit difficult to use in practise to cover the necessary permutations/combinations of materials and settings.

The "problems":

• In my experience it can be very difficult to analyse/interpret the printed result while on the print surface, since there is often a lack of contrast depending on the specifics of the filament and bed surface materials being used (colour, reflectivity, translucency, etc)..
• The K-factor labels often won't print properly/clearly
• The K-factor label elements are tedious to remove/clean from the print surface (#22686)

Are you looking for hardware support?

No, this issue/request is not specific to particular hardware

Describe the feature you want

To be able to remove the entire printed output as a single piece and analyse it off the print surface.

Additional context

I have manually edited an output file from the current standard Marlin generator so as to experiment. I achieved a workable design with no major changes to gcode, which allowed me to remove the entire print from the bed in one piece and then examine it off the print surface.

Fundamentally, I added an attachment line to the frame for each k-factor label, 1mm below them and tails to each number (and dot) to connect them to it and also connected the test area reference markers to the frame.

Below is an image of the printed result after removal from the bed and placed on top of a piece of white paper (there is some shadow caused by the print not lying completely flat on the paper) ->

I thought it would be helpful to share ,so as to at least get feedback and/or further support for such changes and their details.

In the future if I can find the time (I can/do hack but IMHO I'm not proficient in javascript nor html) I will try to implement my changes in a fork of the code and contribute it back.

[thisiskeithb]

Duplicate of MarlinFirmware/MarlinDocumentation#493

[gpread]

Below is a G-code file that produced the image above

LIN_ADV_TEST_0.4Noz_0.2mm_10-50mms_K0_02-0_50_H230_B55.gcode.txt

[Sophist-UK]

I support this improvement - and hope that someone will produce a PR to implement it in the JSON that creates the file.

Can I also ask that the code is improved to ask for the range of frequencies to cover (i.e. lower and upper frequencies) in both types of calibration pattern, in order to allow you to zoom in on the frequency range in question and thus be able to make a more accurate measurement?

Also, the current tool does a constant zigzag shape and varies the feedrate to get the frequency. I was having trouble actually seeing the vibrations on the bedslinger movements on my printer so I tried swapping the X and Y deltas for each step of the zigzag whilst keeping the feedrates the same. (Pythagorus tells us that the line length is the same by swapping X and Y deltas, and so for the same feedrates then the zigzags will take the same time to print and be the same frequencies, the only difference being the magnitude of the vibrations.) It would be helpful, I think, if the tool also allows you to specify the magnitude of vibrations and for it to calculate the appropriate feedrates to match the amplitude and the frequency range.