100 Priority-Encoded Arbiter
100 : Priority-Encoded Arbiter
- Author: Aditya Patra
- Description: Cycles through states based on enable state signals
- GitHub repository
- Open in 3D viewer
- Clock: 10000000 Hz
How it works
This project is a priority-encoded state machine with 4 states. It has 3 enable signals - one corresponding to each of states 1, 2, and 3. In each clock cycle, the project checks whether each enable signal is on in order of priority(states 1 to 3). If an enable signal is found to be on, a counter is used to keep track of how long the signal remains on. If the signal is on for 100000 consecutive clock cycles, the corresponding state is enabled for 100000000 clock cycles.
How to test
To test the project, feed it enable signals from ui_in. ui_in[0] is the enable signal for state 1, ui_in[1] is the enable signal for state 2, and ui_in[2] is the enable signal for state 3. The output state enable signals are sent to the following ports: uo_out[0] is state 1 enabled, uo_out[1] is state 2 enabled, and uo_out[2] is state 3 enabled.
External hardware
No external hardware is necessary for the core functionality of this project, however, the reason I created it is to create a proximity warning system. To create this, you need 3 LIDAR sensors attached to the input ports and 3 buzzers attached to the output ports
IO
| # | Input | Output | Bidirectional |
|---|---|---|---|
| 0 | sensor1 | speaker1 | |
| 1 | sensor2 | speaker2 | |
| 2 | sensor3 | speaker3 | |
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 |