Project case study / 03
TruthScope
A complete sensor-to-browser experiment in live physiological signals.
Exhibited working prototype · Student exhibit · end-to-end prototype
At a glance / inspectable evidence
Project evidence
- Kilobaud stream
- 115.2
- Browser signal
- Live
- TechKnow 2026
- Merit
Sensor data transported from Arduino to Python
Socket.IO updates with session export
Best project / working model recognition
01 / Overview
- Role
- Hardware-to-browser system engineering
- Stack
- Python · Flask · Socket.IO · Arduino · C++
- Recognition
- Best project / working model · TechKnow 2026
A hardware-integrated system that streams galvanic-skin-response readings from Arduino firmware through Python processing into a live web dashboard.
02 / Context & problem
The problem
A compelling real-time exhibit needed reliable acquisition, filtering, threshold-based signal states, transport, visual feedback, and session export across hardware and software boundaries.
The response
TruthScope connects filtered Arduino readings at 115,200 baud to a Flask and Socket.IO backend, then visualises the changing signal in an interactive browser UI.
03 / System path
Follow the work from input to outcome.
- 01
GSR sensor
- 02
Arduino filtering
- 03
Serial stream
- 04
Python processing
- 05
Browser dashboard
04 / Contribution
My contribution.
- 01
Built filtered Arduino acquisition and the 115,200-baud serial stream
- 02
Implemented Python signal processing, threshold-based states, and Socket.IO transport
- 03
Built the browser dashboard, CSV session export, and live demonstration flow
05 / Engineering pressure
The hard parts.
- 01Stabilising noisy physiological readings before applying signal thresholds
- 02Maintaining responsive live updates across the serial and web layers
- 03Packaging a multi-part system for a dependable live demonstration
06 / Outcome & reflection
What came out of it.
Built and demonstrated as a working interactive exhibit, recognised by the TechKnow 2026 committee as a best project and working model.
Lessons carried forward
- Observability is essential when debugging across physical and digital layers.
- A live demo rewards graceful failure paths as much as the main feature.
- Signal presentation should communicate uncertainty, not hide it.