clementinecomputing
36b9f947b2
receiving qr 'fares'
|
4 years ago | |
|---|---|---|
| .. | ||
| DIUv2 | 4 years ago | |
| PIU | 4 years ago | |
| avls | 4 years ago | |
| billdb | 4 years ago | |
| client_supervisor | 4 years ago | |
| commhub | 4 years ago | |
| common | 4 years ago | |
| debug | 4 years ago | |
| gps | 4 years ago | |
| helper | 5 years ago | |
| paddlemgr | 4 years ago | |
| passdb | 4 years ago | |
| ppp-dialer | 6 years ago | |
| rootfs | 4 years ago | |
| scripts | 4 years ago | |
| testing | 6 years ago | |
| README.md | 6 years ago | |
| build_all.sh | 6 years ago | |
| client_modules.list | 6 years ago | |
| configure_target.sh.include | 5 years ago | |
README.md
Driver Interface Unit
This is the main source directory for the Driver Interface Unit (DIU) and Passenger Interface Unit (PIU).
The DIU is driver facing and manages fare collection, server communication, route change, driver login and PIU communication. The PIU manages reading magstripe media, RFID media and rider facing messages through it's display.
Note that this document is a work in progress and is currently incomplete.
Please check back for updates.
Quick Start
To compile:
./build_all.sh native
Binaries will reside in bin/native.
To do a test run, a server must be setup for the DIU to communicate to. For testing, a [test docker server]() can be setup.
The DIU portion is meant to be used on hardware that has both a GPRS, GPS and PIU connected.
To test on a system other than a Raspberry Pi, a test environment has to be setup. To test on the Raspberry Pi, the appropriate system needs to be setup and peripherals attached.
Please check back later for more details.