In order to help debug, a "PIU simulator" should be created in order to push through a variety of fares and fare media that simulates what the PIU would produce.
This is meant to primarily test the electronic connection and not the logical connection.
This means while it might be good to create a PIU simulator that works entirely on the DIU linux machine, that's not what this project is.
This might not need to be done if the PIU replacement comes along fast enough but as a stop gap, there should be testing to make sure the ichthyic and the microcontroller I2C passthrough are functioning properly without dropping any fares.
I'm imagining the following needs to be done for successful completion:
A board to hook up either directly to the microcontroller on board the DIU or through a MAX232 shim
An Arduino (or other microcontroller) on the other side that will simulate a PIU
A schedule of fares and their timings that both the DIU and PIU-simulator agree on to confirm they get pushed through properly
priority
medium
estimate
10 work units
In order to help debug, a "PIU simulator" should be created in order to push through a variety of fares and fare media that simulates what the PIU would produce.
This is meant to primarily test the **electronic** connection and not the logical connection.
This means while it might be good to create a PIU simulator that works entirely on the DIU linux machine, that's not what this project is.
This might not need to be done if the PIU replacement comes along fast enough but as a stop gap, there should be testing to make sure the [ichthyic](https://tree.clementinecomputing.com/clementinecomputing/popufare/src/7adb8bd4399349d9fb835fb49ed6ae018bc8dace/busunit/PIU/shim/ichthyic-passthrough.c) and the [microcontroller I2C passthrough](https://tree.clementinecomputing.com/clementinecomputing/popufare/src/7adb8bd4399349d9fb835fb49ed6ae018bc8dace/busunit/PIU/firmware/ardworker_rcv/ardworker_rcv.ino) are functioning properly without dropping any fares.
I'm imagining the following needs to be done for successful completion:
* A board to hook up either directly to the microcontroller on board the DIU or through a MAX232 shim
* An Arduino (or other microcontroller) on the other side that will simulate a PIU
* A schedule of fares and their timings that both the DIU and PIU-simulator agree on to confirm they get pushed through properly
| | |
|---|---|
| priority | medium |
| estimate | 10 work units |
In order to help debug, a "PIU simulator" should be created in order to push through a variety of fares and fare media that simulates what the PIU would produce.
This is meant to primarily test the electronic connection and not the logical connection. This means while it might be good to create a PIU simulator that works entirely on the DIU linux machine, that's not what this project is.
This might not need to be done if the PIU replacement comes along fast enough but as a stop gap, there should be testing to make sure the ichthyic and the microcontroller I2C passthrough are functioning properly without dropping any fares.
I'm imagining the following needs to be done for successful completion: