Migrated
This commit is contained in:
BIN
Extracurricular/Circuitree/Committee Market/assets/puck_it.png
Normal file
BIN
Extracurricular/Circuitree/Committee Market/assets/puck_it.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 22 KiB |
39
Extracurricular/Circuitree/Committee Market/discussion/CA.md
Normal file
39
Extracurricular/Circuitree/Committee Market/discussion/CA.md
Normal file
@ -0,0 +1,39 @@
|
||||
|
||||
## Redstone computer
|
||||
Do together with people - italic, show and explain in bold
|
||||
|
||||
1. **Basic redstone**
|
||||
- Show and explain the basic components' functions and compare them to real-life electrical components (e.g., wires, switches, diodes).
|
||||
|
||||
2. *Logic gates*
|
||||
- Build basic logic gates using redstone.
|
||||
|
||||
3. *Latches*
|
||||
- simple latches with participants.
|
||||
|
||||
4. *Complex circuit design*
|
||||
- design and assemble more complex circuits
|
||||
|
||||
5. **Combinational Logic Circuit Design**
|
||||
- Build adder and multiplexer
|
||||
|
||||
6. _Storage circuits and memory_
|
||||
|
||||
- Build flip-flops and registers.
|
||||
7. **Cache**
|
||||
- how does retrieval work in memory
|
||||
- the concept of cache with redstone
|
||||
8. _Finite State Machines (FSM)_
|
||||
|
||||
- build a finite state machine
|
||||
9. **The von Neumann Model of Computing**
|
||||
- Idk about this one
|
||||
10. **The data paths implementing the ISA of the LC-3 Processor**
|
||||
- Build data paths
|
||||
11. **Basic Input/Output (Polling); Memory Mapping**
|
||||
|
||||
- I/O redstone
|
||||
12. _I/O by Interrupt_
|
||||
- pressure plates or some shit
|
||||
13. **Making the Leap from Assembly to Higher Level Languages**
|
||||
- redstone -> command blocks?
|
@ -0,0 +1,42 @@
|
||||
|
||||
## Summary
|
||||
|
||||
| Brief description | Difficulty (/10) | Time needed (h) | Estimated fun index (/10) | Manpower (# of ppl) |
|
||||
| ----------------------------------------------------------------- | ---------------- | --------------- | ------------------------- | ------------------- |
|
||||
| [[#Platrix]] | 5 | 5 | 9 | 1-2 |
|
||||
| [[Committee market ideas#Spectrogram image \| Spectrogram image]] | 3 | 2 | 6 | 1 |
|
||||
| [[Committee market ideas#Puck.js bop it \| Puck.js bop it]] | 7 | 5 | 7 | 2 |
|
||||
| [[#Random shit]] | 1 | 2 | 4 | 1 |
|
||||
|
||||
---
|
||||
## Description of ideas
|
||||
### Random shit
|
||||
I will bring my radios, MCUs and other shit like that. Also, I suggest we leave the sticker sheets uncut, so that we add **more** interactivity to our stand (by making people cut their own stickers).
|
||||
|
||||
### Puck.js bop it
|
||||
Have a server, which could be any BT-enabled MCU, which is connected to an 8x8 matrix which shows the following instructions for the 2 players (2 pucks) involved:
|
||||
|
||||
|
||||

|
||||
|
||||
|
||||
The game ends if either of the following conditions are met:
|
||||
- One of the players does the wrong move - the other one wins
|
||||
- One of the players doesn't do the action on time (i.e. takes longer than a second to do it)
|
||||
|
||||
This is going to be really difficult considering:
|
||||
- None of us has significant experience with bluetooth (except maybe serial communication but still)
|
||||
- Even if we do manage to do it, bluetooth is quite unreliable and overall a pain to deal with
|
||||
- We need multiple people to work on this
|
||||
|
||||
### Platrix
|
||||
Working on this [already](https://github.com/CircuitReeRUG/platrix). r/place but irl and on one of these:
|
||||

|
||||
|
||||
### Spectrogram image
|
||||
Have people upload images to a simple webserver (controlled by a raspberry pi/laptop) and display the images on a monitor/laptop. We can transmit with a hackrf/raspi and receive with an SDR stick.
|
||||
|
||||
Here's an example using [spectrum_painter](https://github.com/polygon/spectrum_painter)
|
||||
|
||||
|
||||

|
@ -0,0 +1,14 @@
|
||||
- Pin initialization should be left to the attendees
|
||||
- Encoder is a bit weird
|
||||
|
||||
- Have people be able to write their keystrokes as an array of keys, define that and put into keymap
|
||||
- Functions related to keys
|
||||
- `sendKey(key)`
|
||||
- `sendKeystroke(*keys, int len)`
|
||||
- `getKey`
|
||||
|
||||
- OLED functions
|
||||
- provide them the ssd1306.h file in a digestible way
|
||||
- Encoder function
|
||||
- `getEnc()`
|
||||
-
|
Reference in New Issue
Block a user