How ozkanerbatuhan/hyperloop_pi works
Project type and purpose
• This is a Raspberry-Pi–based, Python–driven IoT/data-acquisition tool (not a web app). It collects accelerometer data from an MPU-6050, controls GPIO pins, and emits data over a serial interface. There is no frontend—it's a single-process embedded script with modular components.
File structure
Top-level files
• main.py – entry point, orchestrates workflow
• mpu6050_sensor.py – encapsulates MPU-6050 I2C interaction
• gpio_control.py – encapsulates RPi.GPIO calls to set/read pins
• serial_data.py – formats and sends measurement packets over UART/USB-serial
• denme.py – likely a test or utility script
• README.md – stub (empty)
• env/.venv – Python virtual environment containing sensor and CLI libraries
Notes
• No separate “src” or “lib” directories—modules live at project root.
• Dependencies installed in virtualenv include RPi.GPIO, adafruit-apds9960, mpu6050_raspberrypi, clint (CLI utilities), args (argument parsing).
README
– It contains no architecture notes. Use code and file names to infer responsibilities.
Be detailed
– Don’t omit any module or hardware interface.
– If there are configuration or test scripts (denme.py), show them off to one side as “utilities.”
[Hardware Layer]
MPU-6050 --I2C--> Raspberry Pi
GPIO Header --pins--> Raspberry Pi
UART--> External Logger/Host
[Software Layer inside Pi]
Python VM ←virtualenv
├── main.py
│ ├→ mpu6050_sensor.py
│ ├→ gpio_control.py
│ └→ serial_data.py
└── denme.py (utility)
[External]
CLI (args/clint) for start-up parameters