A robot is bought, delivered, switched on — and then the greenhouse does not behave the way the demo did. In almost every case the environment, not the machine, is the reason. The good news is that most of the fixes are cheap and can be done while you are still negotiating.
Rails, paths and floors
Pipe rails that are bent, out of level or joined with a step will make a robot stop several times a day. Path width decides whether a machine can turn with a full load, and an uneven floor quietly increases the risk of a loaded arm bouncing. Measure rail level and joint steps before you sign, and write the tolerances into the contract.
Light and vision
Vision systems live or die on contrast. A LED spectrum that flatters human inspectors can wash out a camera, and heavy condensation on the cover makes every image worse. Some suppliers now select varieties and train plants with camera visibility in mind. Ask your robot supplier what spectrum and light level they tested under, and test your own house with their camera.
Crop work matters more than people expect
Truss support, leaf picking and plant guiding determine where the fruit ends up. A crop that is well and evenly guided, with fruit held clear of the wire and the neighbouring plant, can be worth more in robot performance than a faster machine. Agree the crop standard with your supervisor and write it into the pilot plan.
Connectivity and data
Robots need a connection where they work, not where the access point is. Check coverage at the far end of the house, at the plant height where the robot drives, and confirm what happens when the signal drops. Then decide who owns the data and how it reaches your climate computer and labour registration.
A short prep scan before you order — rails, paths, light, crop standard and coverage — usually costs a fraction of a percent of the machine price and decides whether it performs. If you would like us to run that scan with you, email us.