How quecpython/solution-agriculture-control-panel works
Project type and purpose
• This is an embedded, full-stack (firmware + GUI) application—a “Smart Agriculture Central Control Panel” running in QuecPython on the Quectel U-235 EVB hardware.
• Purpose: read environmental sensors (e.g., AHT20), fetch or display weather forecasts, show real-time and historical data curves, control farm equipment, raise alarms, and allow user configuration via a 5″ MIPI LCD.
File structure
• Top-level “code/” directory: all application logic lives here.
• main.py: application entry point and initialization.
• EventMesh.py: internal event bus (pub/sub) for decoupling UI and business logic.
• Agri_ui.py: high–level UI orchestrator, binds screens to events.
• *_screen.py files (welcome, main, monitor, dev1, dev2, alarm, setting1/2, about, weather): individual LVGL screen modules.
• AHT20.py: sensor driver for the AHT20 environmental sensor.
• docs/: architecture illustrations, user guides, and media assets—no code.
• No explicit network modules shown, but weather_screen.py likely uses QuecPython’s HTTP client over the EC600U modem.
README for additional insights
• GUI built on LVGL (embedded graphics library). GUI definitions come from NXP’s GUI Guider (auto-generated code).
• Firmware runs in the QuecPython runtime on the EC600U module.
• Sensors and peripherals are onboard the U-235 EVB; display attaches via MIPI.
• EventMesh is the core pattern for inter-module communication.
Final checklist
• Central EventMesh component.
• Application modules grouped (Agri_ui, sensor driver, individual screens).