Configuring VC3 with Beacon probe should automatically override the Z-Tilt positions to be correct #262
Description
Is your feature request related to a problem? Please describe
A V-core 3 configured through the RatOS wizard to use a Beacon scanner will still use the standard Z-Tilt probing positions that are used with Pinda, BLtouch etc, where the probe is slightly left of the nozzle. These positions do not match where the standard location for a Beacon is, a few mm behind the nozzle.
So it is essentially by default taking readings from around 4 cm away from where it thinks it is, and this error might lead to unnecessary tilt retries.
Describe the solution you'd like
Setting a V-core up with the Beacon through the wizard should automatically override the Z-tilt positions to match where a Beacon probe would be mounted, since their position is as good as standard.
Below are points i use on my VC3.1 400 which work well, for an example.
[z_tilt]
points:
40,20
200,350
360,20
Describe alternatives you've considered
No response
Additional information
This might seem to be a nitpicky suggestion, the Z tilt operation does work despite the error, but also acknowledge that the goal of RatOS 2.1 configurator was that if using common parts, the configurator should be able to automatically generate perfect, functioning config files, and this seems like a further step toward that goal.