Agri-Robot IoT Dashboard Build

TITLE:
Agri-robot data + dashboard: embedded hardware integration and software (phased)

DESCRIPTION:

ABOUT US
we build small electric robots for small farmers in India. They run on battery packs and swap between three attachments: sprayer, crate carrier and weeder. We want to start a field pilot. We want to see, on a dashboard, what each robot is doing in the field, so we can learn how much power each job uses and how well each attachment works.

WHAT WE WANT TO SEE

All robots (every attachment):
- On/working status, location and faults
- Power use of the rover battery and the attachment battery, shown separately, with battery level and remaining run time
- Hours worked, distance travelled and energy used per task

Sprayer:
- Litres sprayed per task and per acre, and tank level
- Spray flow rate and pump on-time
- Area covered
- Alerts for low tank, blocked nozzle or pump fault

Crate carrier:
- Weight carried per trip and total per day
- Number of trips and distance per trip

Weeder:
- Area weeded and hours worked
- Motor load and power use
- Alerts for jam or overload

WHAT WE NEED FROM YOU
Take the data from the robot to a dashboard screen. This is the part we want you to design and recommend:
- The electronics: which sensors, boards and modules to use for each measurement above, and why
- How they are wired and integrated into our robot, including power, protection, and mounting for dust, water and vibration
- How data leaves the field (signal is often weak or absent), and what happens when a robot is offline
- Where the data is stored, and the dashboard
- A parts list with cost per robot, and the monthly running cost for 2 to 3 robots

Please give options where there is a real choice, with your recommendation. We will iterate on the dashboard later, so start with a simple, working version.

PHASES (each paid after we test it on our robot)
Phase 1 (2 to 3 weeks): power use of the rover battery and the attachment battery on a basic dashboard, so we can compare power use across attachments.
Later phases (sprayer, carrier, weeder, then handover) are agreed after Phase 1 is accepted.
Target: a working basic version in 1-2 months.

WHAT WE ALREADY HAVE
- A basic prototype that reads battery data and shows it on a dashboard. Reuse it or replace it.
- Two separate lithium battery sets, one for the rover and one for the attachment. Each has its own intelligent BMS (battery management system).
- Each battery a.60V and b. 29v brings out four communication wires: CAN (CAN H, CAN L) and RS485 (A, B), plus power on an XT90 connector. (UART might also be available in near future).
- BMS make and model: [add here]. We will share the protocol document after an NDA.
Please tell us which port (CAN or RS485) you would use to read the battery data, and why.

MUST HAVE
Experience in both embedded hardware and software/cloud, and with field systems on poor connectivity. You may be a single freelancer or a team. Agriculture experience is a plus.

OWNERSHIP
We own all code, designs and data. Code goes to our repository from day one, with handover documentation.

IN YOUR PROPOSAL, TELL US
1. Your approach in plain words, including the electronics you would choose
2. Phase 1 price and timeline, plus estimated price for later phases
3. Parts cost per robot and monthly running cost for 2 to 3 robots
4. Which battery port and interface hardware you would use
5. Solo or team, and who does the hardware
6. Similar work you have delivered (links)
7. What you need from us, and the main risk you see

BUDGET: Open to quotes
DURATION: 1- 2 months and shall be extended based on deliverables phase wise.
SKILLS: IoT, Embedded Systems, ESP32, Firmware, CAN Bus, RS485, Cloud, Dashboard, React, Python