How m3s-kuura/toyota-data-feeder works
A small demo replays Toyota RAV4 Hybrid signals from a CSV as MQTT messages. Its runtime configures a TLS MQTT client, waits for broker connection, then repeatedly reads timed rows and publishes non-empty signal values to client-specific topics. The README documents the data, topic format and broker settings; callbacks and CSV playback are implemented in feeder.py. The README also mentions original and generated CAN/DBC assets, but they are inputs/background rather than separate runtime stages shown in source.
Main entry points: feeder.py Feeder entry point · toyota_data.csv Mapped vehicle signals
Components 9
Playback and publishing
- Feeder entry point
feeder.py - MQTT TLS setup
feeder.py - Connection callbacks
feeder.py - CSV playback
feeder.py
Vehicle data
- Mapped vehicle signals
toyota_data.csv - Original vehicle log
assets/toyota_data_original.csv - RAV4 Hybrid DBC
assets/toyota_rav4_hybrid_2017_pt_generated.dbc
Other components
- Operator
- MQTT broker
Connections 8
- Operator → Feeder entry point: runs
readme.md - Feeder entry point → MQTT TLS setup: configures
feeder.py - MQTT TLS setup → MQTT broker: connects securely
feeder.py - MQTT TLS setup → Connection callbacks: registers
feeder.py - Feeder entry point → Connection callbacks: waits for status
feeder.py - Feeder entry point → CSV playback: starts after connection
feeder.py - CSV playback → Mapped vehicle signals: reads repeatedly
feeder.py - CSV playback → MQTT broker: publishes signal topics
feeder.py