Expose MIN_SPEED from create_vibrations_profile.py as a user editable variable for the create_vibrations_profile macro

[lanpartyceo]

Describe the feature or hardware support you'd like

Mahine: KLP1
Processor: Rockchip (of some form, unknown model)
RAM: 1GB
EMMC: 32GB

While initially functional on the machine, the create_vibrations_profile eventually stopped working as I increased the numbers to the machines limits. I was unable to get past the initial 2mm/s motion without throwing this error that seemed indicative/similar to a "timer too close" type of error:

TimeoutError: Shake&Tune was unable to retrieve accelerometer data in time. This might be due to slow hardware or a busy system.
Transition to shutdown state: Internal error on command:"_CREATE_VIBRATIONS_PROFILE"

After which klipper just had the error: UNKNOWN in the red error box on the main web interface window

after which the system needed to be rebooted as the restart and firmware restart did not "unfreeze" whatever component had been the cause. Maybe due to being unable to reset the toolhead board independently.

Whatever the reason there, it highlights that there may still be a time delay issue on some under powered systems.

As I had noticed that no matter what i changed in the available settings for the create_vibrations_profile macro it always started at 2 mms, i found the associated .py file and changed the minimum speed to 10mms (which is a more realistic minimum speed that a printer would print at rather than 2mms, IMO)

Changing this has allowed all subsequent runs of the create_vibrations_profile macro to complete without issue, as well as providing a more logical scale for testing (10, 20, 30 mms, etc vs 2, 12, 22 mms , etc). This is likely due to the movement now being fast enough to either generate enough continuous data such that a comms timeout was never seen, or simply due to the fact the testing command could complete before the timeout error could occur, allowing the processing of the data collection.

So, based on the fact that this solves additional timeout issues that still seem to be prevalent on low end systems given the correct scenario, and rather than let the repo be dirty and have the fix undone on updates I am requesting that the MIN_SPEED variable be made one of the user modifiable variables of the create_vibrations_profile macro list show below.

Additional context or information

No response

[dclift97]

I also had issues with this. Changing the default MIN_SPEED value does solve the issue, and seems to be an easy enhancement.

[TigreBois]

I can corroborate; I ran into this problem as I increased the SIZE to 150 for measuring higher speeds, and it would error out as described. Increasing MIN_SPEED in create_vibration_profile.py to 10 does not trigger the error.

[Frix-x]

This was added in the latest commit in the develop branch and will be released in the next version :)