07Engineering project2025

Computer vision and sensing

AI + IoT crop surveillance

A crop-monitoring prototype connecting YOLOv11 computer vision with LoRaWAN sensing during an IIT Delhi-associated R&D internship.

R&D internship prototype

The system connected image-based crop monitoring with low-power communication, forcing model behaviour, sensors and field conditions to be considered together.

Research question

How can a vision model and constrained IoT link operate as one field prototype rather than two disconnected demos?

My contribution

  • Developed the AI + IoT prototype during a January–June 2025 R&D internship.
  • Integrated YOLOv11-based crop monitoring with LoRaWAN communication.
  • Iterated on the model/data pipeline after lighting changes caused a weed misclassification.

Signature view

Trace the evidence.

Move across the research chain. The case study below remains complete and readable without this interaction.

01

Question

Join perception to a field system

Useful crop monitoring requires sensing, inference and constrained communication to work together.

Prototype context: an R&D internship.

Method, as a sequence of decisions

  1. 01

    Capture field imagery and sensor context.

  2. 02

    Run YOLOv11-based crop/anomaly detection.

  3. 03

    Transmit relevant observations over LoRaWAN.

  4. 04

    Inspect field failures and revise data/model assumptions.

Working setYOLOv11LoRaWANIoTComputer vision

What the record actually supports

6 months

R&D internship period

January–June 2025 in the recovered record.

YOLOv11

Vision foundation

Used for crop segmentation/anomaly detection.

LoRaWAN

Field connectivity

Low-power communication integrated into the prototype.

Evidence: CVs and UCD statement of purpose. IIT Delhi A.I.C./Aapah host wording needs certificate reconciliation.

Choices and trade-offs

R1

Why inspect field errors?

Lighting variation exposed a weed misclassification, illustrating why deployment conditions belong inside the research loop.

What has not been established

  • Exact host/employer wording awaits the internship certificate.
  • No field-scale accuracy or reliability benchmark is claimed.
  • The prototype record does not establish production deployment.

What I would investigate next

  1. Q1How should the data pipeline represent lighting and seasonal drift?
  2. Q2Which decisions should run locally versus across the LoRaWAN link?

No public paper or repository is attached yet. The case study is intentionally limited to the evidence in the supplied record.

Next study · 08ReAttire learning platform