Skip to content
Aglier logo

Robotics · Research · Agentic AI

Aglier: inside an AI tree-climbing fruit-harvesting robot

How Aglier climbs a trunk, decides which fruit is ripe and picks it in five timed stages, with the claw geometry and cycle-time maths behind the design.

Adithya Reddy · · Updated · 5 min read

Annotated patent drawing of the Aglier tree-climbing fruit-harvesting robot clamped to a trunk with four clamps, showing the AI camera module, articulated arm, gripper, collection basket, battery pack and communication module.
FIG. 9: Annotated view of the robot (Cam Bot). Four clamps hold the trunk; the arm, gripper and basket do the picking.

Aglier is a robot that climbs a fruit tree, finds ripe fruit with an onboard camera, picks it and drops it into a basket it carries. I am its sole inventor and I'm drafting the patent specification. The figures in this post come from that specification.

This article covers what the robot is made of, how it holds onto a trunk, how long one pick takes, and where AI fits in. The numbers are the representative ranges in the drawings. They show how the design is reasoned, not field-test results.

What the robot is made of

The annotated view labels every major part with a reference numeral. They group into four jobs:

Job Parts
Hold the tree Four clamps: upper (30a), second (30b), third (30c), lower (30d)
See Camera module with AI (20): wide-angle camera for navigation (21), depth sensor for distance (22), LED illuminator for low light (23)
Pick Articulated arm (40), end-effector gripper (80), collection basket (50)
Run Main body and control unit (10), battery pack (60), communication module over Wi-Fi, 4G, 5G or LoRa (70)

Four independent clamps let the robot keep hold of the trunk while it repositions. The depth sensor matters as much as the camera. Knowing that an apple is ripe is useless unless the arm also knows how far away it is.

How Aglier grips a trunk: the closure-angle equation

Trunks vary in thickness, so a clamp can't close to a fixed position. Each claw pair pivots until its tips touch the bark. FIG. 3 shows the geometry.

Geometry of a claw pair closing around a tree trunk, showing claw length L, trunk radius r and closure angle theta, with the relationships r = L sin(theta/2) and theta = 2 arcsin(r/L).
FIG. 3: A claw pair closing on a trunk of radius r. Each arm has length L; θ is the closure angle between the claw tips.

Half of the claw pair forms a right triangle. The claw arm of length LL is the hypotenuse, the trunk radius rr is the opposite side, and the angle at the pivot is θ/2\theta/2. So:

r=Lsin⁡(θ2)⟺θ=2 sin⁡−1 ⁣(rL)r = L \sin\left(\frac{\theta}{2}\right) \qquad\Longleftrightarrow\qquad \theta = 2\,\sin^{-1}\!\left(\frac{r}{L}\right)

The relationship works in both directions, which is the useful part:

  • Radius to angle: given the trunk radius, the controller knows how far to close the claws.
  • Angle to radius: the joint angle is measurable, so once the claws touch bark the robot can calculate the trunk's radius from it. The drawing labels rr as the sensed trunk radius for this reason.

Only the ratio r/Lr/L matters, so the curve below holds for any claw length:

Closure angle needed for each trunk-radius-to-claw-length ratio
0°45°90°135°180°00.20.40.60.81 r / L (trunk radius ÷ claw length) = 0.5 → Closure angle θ ≈ 60° 60°r / L (trunk radius ÷ claw length) = 0.71 → Closure angle θ ≈ 90° 90°r / L (trunk radius ÷ claw length) = 0.87 → Closure angle θ ≈ 120° 120° r / L (trunk radius ÷ claw length) Closure angle θ

θ = 2·arcsin(r/L). The curve steepens as r approaches L, so small radius errors cause large angle changes near the limit.

View the data as a table
r / L (trunk radius ÷ claw length)Closure angle θ
00°
0.223.1°
0.447.2°
0.560°
0.673.7°
0.7190°
0.8106.3°
0.87120°
1180°

Three reference points make it concrete. A trunk whose radius is half the claw length needs 60∘60^\circ; at r/L≈0.71r/L \approx 0.71 the claws sit at 90∘90^\circ; at r/L≈0.87r/L \approx 0.87 they need 120∘120^\circ.

Why the steep end of the curve is a design constraint

Differentiating the closure equation shows how sensitive the angle is to radius:

dθdr=2L1−(r/L)2\frac{d\theta}{dr} = \frac{2}{L\sqrt{1 - (r/L)^2}}

As r/L→1r/L \to 1 the denominator goes to zero and the sensitivity grows without bound. Near that limit, a millimetre of sensing error means a large change in claw angle, and the grip gets unreliable. At r=Lr = L the claws are fully open (θ=180∘\theta = 180^\circ) and the pair can't wrap the trunk at all.

The practical rule follows directly: choose a claw length well above the largest trunk radius the robot must climb, so it always works on the flatter part of the curve.

Six ways to hold onto bark

Bark ranges from smooth to deeply furrowed, so the specification covers six alternative ways to engage it.

Six alternative bark-engagement designs: claw friction clamp, microspine array, hybrid adhesive and microspine foot, tendon-driven wrap gripper, wheeled spring-cinch mechanism and pneumatic flexible clamp.
FIG. 5: Alternative bark-engagement embodiments, from high-friction claws to pneumatic clamps.
Embodiment How it grips
(A) Claw / friction clamp Articulated claw arms with high-friction pads
(B) Microspine array Many small spines that catch in bark texture
(C) Hybrid adhesive + microspine foot Spines for mechanical grip plus an adhesive layer for extra traction
(D) Continuum / tendon-driven wrap gripper Flexible segments that wrap the trunk, opened and closed by a tendon drive
(E) Wheeled / tracked spring-cinch Wheels or tracks on the bark, held closed by a spring-cinch mechanism
(F) Pneumatic flexible clamp Inflatable bladders pressed against the trunk through an air supply line

Covering several mechanisms protects the invention against a single design choice. It also reflects reality: no single gripper suits every tree.

The five-stage harvest cycle, timed

Every fruit goes through the same sequence. FIG. 14 gives a representative time range for each stage and the part of the robot responsible for it.

Timing diagram of the per-fruit harvest cycle in five stages: climb and reposition, vision confirmation and AI decision, manipulator approach, cut or grasp, and transfer to the basket, with a structured event log feeding the GBNI narrative tier.
FIG. 14: Per-fruit harvest cycle. Timings are illustrative; real durations depend on trunk geometry, fruit position, vision confidence, actuator speed and conditions.
Representative time range for each stage of one fruit pick
024681012 1. Climb / reposition: 2–5 s (clamps 30a–30d) 1. Climb / reposition 2–5 s 2. Vision + AI decision: 0.2–0.8 s (vision / AI module 20) 2. Vision + AI decision 0.2–0.8 s 3. Arm approach: 0.5–1.8 s (articulated arm 40) 3. Arm approach 0.5–1.8 s 4. Cut / grasp: 0.5–2.8 s (end-effector) 4. Cut / grasp 0.5–2.8 s 5. Transfer / release: 0.5–1.5 s (collection basket 50) 5. Transfer / release 0.5–1.5 s Full cycle: 3.7–11.9 s (Sum of the stage ranges) Full cycle 3.7–11.9 s seconds

Ranges from FIG. 14. The total row adds the stage minimums and maximums.

View the data as a table
StageMin (s)Max (s)
1. Climb / reposition25
2. Vision + AI decision0.20.8
3. Arm approach0.51.8
4. Cut / grasp0.52.8
5. Transfer / release0.51.5
Full cycle3.711.9

What the timing budget tells us

Adding the stages gives the cycle-time bounds:

Tmin⁡=2+0.2+0.5+0.5+0.5=3.7 sTmax⁡=5+0.8+1.8+2.8+1.5=11.9 sT_{\min} = 2 + 0.2 + 0.5 + 0.5 + 0.5 = 3.7\ \text{s} \qquad T_{\max} = 5 + 0.8 + 1.8 + 2.8 + 1.5 = 11.9\ \text{s}

If every fruit needed a full cycle, the implied throughput would be:

3600 s/h11.9 s≈303to3600 s/h3.7 s≈973 fruit per hour\frac{3600\ \text{s/h}}{11.9\ \text{s}} \approx 303 \quad\text{to}\quad \frac{3600\ \text{s/h}}{3.7\ \text{s}} \approx 973\ \text{fruit per hour}

That's arithmetic on illustrative ranges, not measured performance. It still exposes the design priority. Climbing and repositioning take 2/3.7≈54%2/3.7 \approx 54\% of the fastest cycle and 5/11.9≈42%5/11.9 \approx 42\% of the slowest, making it the largest single stage in both cases. The AI decision itself is the smallest, at most 0.80.8 seconds.

Where the AI sits, and where it doesn't

Stage 2 is where AI makes the real-time call. The camera module confirms a fruit is ripe and reachable, and the depth sensor gives the arm its target.

The second role is quieter. Each completed cycle is time-stamped and written to a structured event log. Batch-level records from that log may later feed an asynchronous GBNI narrative tier, which turns harvest data into readable summaries. The specification is explicit that this path does not control the real-time harvest cycle.

That separation is deliberate. Clamping and cutting must never wait on a language model. Keeping narrative generation off the control loop means a slow or unavailable AI summary can't affect safety or timing. GBNI is my state-aware agent framework; I explain it in GBNI, briefly.

Frequently asked questions

What is Aglier?

Aglier is an AI-integrated robot that climbs fruit trees and harvests fruit. It grips the trunk with four clamps, uses an AI camera module with a depth sensor to find ripe fruit, and picks it with an articulated arm and gripper into an onboard basket.

How does a tree-climbing robot grip trunks of different sizes?

Each claw pair pivots until its tips meet the bark. The closure angle follows θ=2sin⁡−1(r/L)\theta = 2\sin^{-1}(r/L), where rr is the trunk radius and LL the claw length. Reading the angle back also lets the robot calculate the trunk's radius.

How long does Aglier take to pick one fruit?

The specification's representative ranges add up to about 3.7 to 11.9 seconds per fruit across five stages: climb, vision decision, arm approach, cut or grasp, and transfer. These are illustrative; real times depend on the tree and conditions.

Does the AI control the robot's movements?

The AI camera module makes the real-time ripeness and targeting decision. The GBNI narrative tier only reads batch records from the event log afterwards and never controls the harvest cycle.

Is Aglier patented?

Adithya Reddy is the sole inventor and is drafting the patent specification. The figures in this article come from that specification.