We’ve made a note of this for a future release. Thanks for the feature request.
If I am understanding your question, I believe this would require you to just set the correct axis length / home position in the device settings page. You might also be able to adjust the belt endstops so that the motor does not go past a certain point. Please let me know if this is not what you meant. The software currently does not support “no travel zones” in the X/Y axis, though that is something we want to add to a future app release. We partially support no travel zones in the Z axis by way of the “SAFE HEIGHT” setting.
We could do this, but I don’t think this is a good idea. the 1,000 point limit is not an artificial limit or a limit imposed for business reasons. The limit was created based on testing we did a few years ago about what a “reasonable load” was for an Express device.
Once the spring rush dies down, we hope to do a big refactor of the FBOS code relating to plant limits. Hopefully, we can change things then, assuming that performance tuning will make the DB more performant on the FBOS side.
Since you mentioned in a different thread that you are a software developer, I can point you to some comments I left in the codebase in 2019 that explain our decision to cap points at 1000: Farmbot-Web-App/create.rb at staging · FarmBot/Farmbot-Web-App · GitHub
class Create < Mutations::Command
# WHY 1000?:
# * This limit is placed for _technical_
# reasons, not business reasons. If it were
# reasonable to have that many points, we
# would certainly allow it. Real world use
# has shown that devices cannot support this
# many points (CPU limits).
# * 2019 RPis + Frontend UI cannot reliably
# handle > 1000 points.
# * Bots with > 800 points are outliers. Most
# users simply don't have that many plants
# * An XL bot at 100% capacity and 1000
# evenly space plants = 5 inch point grid.
# Smaller bed = higher resolution.