Set hybrid edit range to 999

[vovodroid]

Currently TMC hybrid threshold is edited as uint8. This PR uses unit16 and range up to 999.

P.S. Should min value be >0?

[thinkyhead]

The description from ChatGPT is below. In practice, Marlin uses the values specified by the TMCStepper library and not necessarily the native range of the stepper drivers. So we need to look first at how TMCStepper interprets these values for all the stepper drivers that it supports, and then adjust the code so it can adapt to the type of stepper drivers that are installed.

---

The Hybrid Threshold on Trinamic stepper drivers determines the speed at which the driver switches between stealthChop (quiet mode) and spreadCycle (performance mode). Different models of Trinamic drivers have different ranges for this parameter. Here is a summary of the ranges for some common Trinamic drivers:

• TMC2130: The Hybrid Threshold value can range from 0 to 65535. This corresponds to a step frequency threshold where switching between modes occurs.

• TMC2208 / TMC2225: The Hybrid Threshold value typically ranges from 0 to 255 steps per second. These drivers are commonly used in silent 3D printers, and the range is narrower compared to other models.

• TMC2209: Like the TMC2208, it also supports a range from 0 to 255 steps per second for the Hybrid Threshold.

• TMC2660: This driver allows setting the Hybrid Threshold up to 65535 steps per second, providing a broad range for switching between stealthChop and spreadCycle modes.

• TMC5160: The range for Hybrid Threshold on this model is from 0 to 65535, similar to the TMC2130 and TMC2660.

The specific threshold values you set depend on the application, such as the speed and torque requirements of your setup. Higher thresholds keep the motor in stealthChop longer, which is quieter but less powerful, while lower thresholds switch to spreadCycle earlier, providing more torque at higher speeds.

[vovodroid]

But in Marlin this parameter is just speed, isn't it? So it could be in any reasonable speed value (zero means disabled according ro datasheet).

[thinkyhead]

Yes, it does appear that the value is transformed.

12,650,000 * microsteps / (256 * thrs * steps_per_mm)

…however it doesn't appear to be scaled based on the driver type. If the driver type has a range from 0 to 65535, then presumably the value should be scaled to that range as well before sending it to TPWMTHRS. I'm looking into it. Possibly @teemuatlut can provide some guidance.